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. 56 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 1 caught line
Download .patchdiff --git a/gateway/src/readme-text.ts b/gateway/src/readme-text.ts --- a/gateway/src/readme-text.ts +++ b/gateway/src/readme-text.ts @@ -166,1 +166,0 @@ -\`MINERU_S2S_BEARER\` 禁止复用前端旧 MinerU Key、RapidAPI/proxy token 或任何旧网关 Key。只通过 \`wrangler secret put\` 或本地 \`.dev.vars\` 设置，不要写进 \`wrangler.jsonc\`、源码、测试或 README。
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of r1. 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: mcp-imgkits: Credential pass-through configuration (KillerSkills verdict caution 56)
## What the honeypot observed
KillerSkills ran **mcp-imgkits@r1** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 56/100**. Summary: static analysis only — behavior not yet observed.
- See the findings below.
Full trace and findings: https://killerskills.ai/skills/glama/mcp-imgkits/r1
## Findings with a location
- `gateway/src/readme-text.ts:166` · Credential pass-through configuration — gateway/src/readme-text.ts:166 · Credential pass-through configuration — agent relays sensitive credentials
## Proposed change
The attached patch removes the 1 line 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 yichong1/mcp-imgkits --clone && cd mcp-imgkits curl -s https://killerskills.ai/skills/glama/mcp-imgkits/r1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/r1 && git commit -am "mcp-imgkits: Credential pass-through configuration" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/mcp-imgkits/r1/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.