← print-mcp@1.1.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. 77 · Caution

Evidence

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

Diff · removes 3 caught lines

Download .patch
diff --git a/src/test/setup.test.ts b/src/test/setup.test.ts
--- a/src/test/setup.test.ts
+++ b/src/test/setup.test.ts
@@ -92,1 +92,0 @@
-const good = s.write(path.join('.codeium', 'windsurf', 'mcp_config.json'), '{}');
diff --git a/web/public/elements.js b/web/public/elements.js
--- a/web/public/elements.js
+++ b/web/public/elements.js
@@ -48,1 +48,0 @@
-…🥇🎯🎵🎶⚽🏀🎮✅❌⚠️❓❗➕➖➡️⬅️⬆️⬇️♻️©️®️™️'.match(/\p{Extended_Pictographic}(?:️)?(?:‍\p{Extended_Pictographic}️?)*|✅|❌/gu) ?? []; let libs = {}; const loadScript = …
diff --git a/src/cli.ts b/src/cli.ts
--- a/src/cli.ts
+++ b/src/cli.ts
@@ -73,1 +73,0 @@
-const text = fs.readFileSync(file, 'utf8').replace(/^/, '');

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.1.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: print-mcp: Hidden zero-width characters detected (KillerSkills verdict caution 77)

## 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 77/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/print-mcp/1.1.0

## Findings with a location
- `src/test/setup.test.ts:92` · Hidden zero-width characters detected — src/test/setup.test.ts:92 · Hidden zero-width characters detected — may conceal content
- `web/public/elements.js:48` · Hidden zero-width characters detected — web/public/elements.js:48 · Hidden zero-width characters detected — may conceal content
- `src/cli.ts:73` · Hidden zero-width characters detected — src/cli.ts:73 · Hidden zero-width characters detected — may conceal content

## Proposed change
The attached patch removes the 3 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 Kritsanai-Krish/print-mcp --clone && cd print-mcp
curl -s https://killerskills.ai/skills/glama/print-mcp/1.1.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.1.0 && git commit -am "print-mcp: Hidden zero-width characters detected"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/print-mcp/1.1.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.