← markitdown-file-converter@1.0.0

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 57 · Caution

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 14 caught lines

Download .patch
diff --git a/scripts/backends/pandoc.py b/scripts/backends/pandoc.py
--- a/scripts/backends/pandoc.py
+++ b/scripts/backends/pandoc.py
@@ -1,1 +1,0 @@
-#!/usr/bin/env python3
diff --git a/scripts/ocr/__init__.py b/scripts/ocr/__init__.py
--- a/scripts/ocr/__init__.py
+++ b/scripts/ocr/__init__.py
@@ -1,1 +1,0 @@
-# OCR Engines package
diff --git a/scripts/backends/mammoth.py b/scripts/backends/mammoth.py
--- a/scripts/backends/mammoth.py
+++ b/scripts/backends/mammoth.py
@@ -1,1 +1,0 @@
-#!/usr/bin/env python3
diff --git a/scripts/ocr/engine.py b/scripts/ocr/engine.py
--- a/scripts/ocr/engine.py
+++ b/scripts/ocr/engine.py
@@ -1,1 +1,0 @@
-#!/usr/bin/env python3
diff --git a/scripts/backends/__init__.py b/scripts/backends/__init__.py
--- a/scripts/backends/__init__.py
+++ b/scripts/backends/__init__.py
@@ -1,1 +1,0 @@
-# Backends package
diff --git a/scripts/ocr/selector.py b/scripts/ocr/selector.py
--- a/scripts/ocr/selector.py
+++ b/scripts/ocr/selector.py
@@ -1,1 +1,0 @@
-#!/usr/bin/env python3
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -1,1 +1,0 @@
----
diff --git a/scripts/__init__.py b/scripts/__init__.py
--- a/scripts/__init__.py
+++ b/scripts/__init__.py
@@ -1,1 +1,0 @@
-# Scripts package
diff --git a/scripts/main.py b/scripts/main.py
--- a/scripts/main.py
+++ b/scripts/main.py
@@ -1,1 +1,0 @@
-#!/usr/bin/env python3
diff --git a/scripts/backends/markitdown.py b/scripts/backends/markitdown.py
--- a/scripts/backends/markitdown.py
+++ b/scripts/backends/markitdown.py
@@ -1,1 +1,0 @@
-#!/usr/bin/env python3
diff --git a/scripts/ocr/rapidocr.py b/scripts/ocr/rapidocr.py
--- a/scripts/ocr/rapidocr.py
+++ b/scripts/ocr/rapidocr.py
@@ -1,1 +1,0 @@
-#!/usr/bin/env python3
diff --git a/scripts/ocr/paddleocr.py b/scripts/ocr/paddleocr.py
--- a/scripts/ocr/paddleocr.py
+++ b/scripts/ocr/paddleocr.py
@@ -1,1 +1,0 @@
-"""PaddleOCR Cloud API integration."""
diff --git a/scripts/utils/deps.py b/scripts/utils/deps.py
--- a/scripts/utils/deps.py
+++ b/scripts/utils/deps.py
@@ -1,1 +1,0 @@
-#!/usr/bin/env python3
diff --git a/scripts/utils/cleanup.py b/scripts/utils/cleanup.py
--- a/scripts/utils/cleanup.py
+++ b/scripts/utils/cleanup.py
@@ -1,1 +1,0 @@
-#!/usr/bin/env python3

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.0. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: markitdown-file-converter: Hidden zero-width characters detected (KillerSkills verdict caution 57)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 57/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/markitdown-file-converter/1.0.0

## Findings with a location
- `scripts/backends/pandoc.py:1` · Hidden zero-width characters detected — scripts/backends/pandoc.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/ocr/__init__.py:1` · Hidden zero-width characters detected — scripts/ocr/__init__.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/backends/mammoth.py:1` · Hidden zero-width characters detected — scripts/backends/mammoth.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/ocr/engine.py:1` · Hidden zero-width characters detected — scripts/ocr/engine.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/backends/__init__.py:1` · Hidden zero-width characters detected — scripts/backends/__init__.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/ocr/selector.py:1` · Hidden zero-width characters detected — scripts/ocr/selector.py:1 · Hidden zero-width characters detected — may conceal content
- `SKILL.md:1` · Hidden zero-width characters detected — SKILL.md:1 · Hidden zero-width characters detected — may conceal content
- `scripts/__init__.py:1` · Hidden zero-width characters detected — scripts/__init__.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/main.py:1` · Hidden zero-width characters detected — scripts/main.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/backends/markitdown.py:1` · Hidden zero-width characters detected — scripts/backends/markitdown.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/ocr/rapidocr.py:1` · Hidden zero-width characters detected — scripts/ocr/rapidocr.py:1 · Hidden zero-width characters detected — may conceal content
- `scripts/ocr/paddleocr.py:1` · Hidden zero-width characters detected — scripts/ocr/paddleocr.py:1 · Hidden zero-width characters detected — may conceal content

## Proposed change
The attached patch removes the 14 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._
# or from a terminal, under your own account:
gh repo fork oschwartz10612/poppler-windows --clone && cd poppler-windows
curl -s https://killerskills.ai/skills/clawhub/markitdown-file-converter/1.0.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.0.0 && git commit -am "markitdown-file-converter: Hidden zero-width characters detected"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/markitdown-file-converter/1.0.0/patch.md)

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.