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. 68 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 2 caught lines
Download .patchdiff --git a/security_audits/2026-09-25_a80b830/coverage-ledger.json b/security_audits/2026-09-25_a80b830/coverage-ledger.json --- a/security_audits/2026-09-25_a80b830/coverage-ledger.json +++ b/security_audits/2026-09-25_a80b830/coverage-ledger.json @@ -1173,1 +1173,0 @@ -…owedDomains [] in Docker weaker-nested mode, sandboxed code holding the per-run proxy credential (exposed in HTTP_PROXY/ALL_PROXY) must not reach the MCP server port in the con… @@ -1836,1 +1835,0 @@ -…sts and the default srt settings content, which has no secrets. The srt per-run proxy credential is created inside srt and is never logged by this code. The Popen env is only P…
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: mcp-run-isolated-python: Credential pass-through configuration (KillerSkills verdict caution 68)
## 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 68/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/pypi/mcp-run-isolated-python/1.1.0 ## Findings with a location - `security_audits/2026-09-25_a80b830/coverage-ledger.json:1836` · Credential pass-through configuration — security_audits/2026-09-25_a80b830/coverage-ledger.json:1836 · Credential pass-through configuration — agent relays sensitive credentials - `security_audits/2026-09-25_a80b830/coverage-ledger.json:1173` · Credential pass-through configuration — security_audits/2026-09-25_a80b830/coverage-ledger.json:1173 · Credential pass-through configuration — agent relays sensitive credentials ## 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 Kigstn/mcp-run-isolated-python --clone && cd mcp-run-isolated-python curl -s https://killerskills.ai/skills/pypi/mcp-run-isolated-python/1.1.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.1.0 && git commit -am "mcp-run-isolated-python: Credential pass-through configuration" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/mcp-run-isolated-python/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.