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. 78 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/src/tools/mogrt-bake.ts b/src/tools/mogrt-bake.ts
--- a/src/tools/mogrt-bake.ts
+++ b/src/tools/mogrt-bake.ts
@@ -298,1 +298,0 @@
-const definition = JSON.parse(definitionEntry.data.toString("utf8").replace(/^/, "")) as Record<string, any>;
@@ -368,1 +367,0 @@
-if (entry.name === "definition.json") output.push({ name: entry.name, data: Buffer.from("" + JSON.stringify(definition), "utf8") });
diff --git a/src/ai/caption-retime.ts b/src/ai/caption-retime.ts
--- a/src/ai/caption-retime.ts
+++ b/src/ai/caption-retime.ts
@@ -81,1 +81,0 @@
-return /^?WEBVTT(?:[ \t]|\r?\n|$)/.test(content) ? "vtt" : "srt";
@@ -89,1 +88,0 @@
-const lines = content.replace(/^/, "").replace(/\r\n?/g, "\n").split("\n");
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.3.1. 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: premiere-mcp-imt: Hidden zero-width characters detected (KillerSkills verdict caution 78)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 78/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/glama/premiere-mcp-imt/1.3.1 ## Findings with a location - `src/tools/mogrt-bake.ts:368` · Hidden zero-width characters detected — src/tools/mogrt-bake.ts:368 · Hidden zero-width characters detected — may conceal content - `src/tools/mogrt-bake.ts:298` · Hidden zero-width characters detected — src/tools/mogrt-bake.ts:298 · Hidden zero-width characters detected — may conceal content - `src/ai/caption-retime.ts:81` · Hidden zero-width characters detected — src/ai/caption-retime.ts:81 · Hidden zero-width characters detected — may conceal content - `src/ai/caption-retime.ts:89` · Hidden zero-width characters detected — src/ai/caption-retime.ts:89 · Hidden zero-width characters detected — may conceal content ## Proposed change The attached patch removes the 4 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 Immersive-Media-Technologies/premiere-mcp-imt --clone && cd premiere-mcp-imt curl -s https://killerskills.ai/skills/glama/premiere-mcp-imt/1.3.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.3.1 && git commit -am "premiere-mcp-imt: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/premiere-mcp-imt/1.3.1/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.