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 2 caught lines
Download .patchdiff --git a/test/checks.test.mjs b/test/checks.test.mjs
--- a/test/checks.test.mjs
+++ b/test/checks.test.mjs
@@ -322,1 +322,0 @@
-const script = `fetch("http://localhost:3000/api/items");const pk="pk_\u0074est_aB3dE6gH9jK2mN5pQ8sT1vW4";fetch("https://api.openai.com/v1/chat/completions");send({from:"[email protected]"});`;
diff --git a/site/blockers/index.html b/site/blockers/index.html
--- a/site/blockers/index.html
+++ b/site/blockers/index.html
@@ -170,1 +170,0 @@
-<summary>Does my code get uploaded?</summary><p>No. Everything runs on your computer. Names in <code>.env</code> files are read, never values.</p>
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.4.4. 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: greenlitlab: URL with embedded credentials (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/glama/greenlitlab/0.4.4 ## Findings with a location - `test/checks.test.mjs:322` · URL with embedded credentials — test/checks.test.mjs:322 · URL with embedded credentials — may be phishing or credential leaking - `site/blockers/index.html:170` · Collapsed <details> block carrying instructions — site/blockers/index.html:170 · Collapsed <details> block carrying instructions · informational: not an instruction file ## Proposed change The attached patch removes the 2 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 priberry-data/greenlitlab --clone && cd greenlitlab curl -s https://killerskills.ai/skills/glama/greenlitlab/0.4.4/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.4.4 && git commit -am "greenlitlab: URL with embedded credentials" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/greenlitlab/0.4.4/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.