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 3 caught lines
Download .patchdiff --git a/src/unitmcp/orchestrator/shell.py b/src/unitmcp/orchestrator/shell.py --- a/src/unitmcp/orchestrator/shell.py +++ b/src/unitmcp/orchestrator/shell.py @@ -308,1 +308,0 @@ ---ssh-key-path=<path> Path to SSH key (default: ~/.ssh/id_rsa) @@ -613,1 +612,0 @@ ---ssh-key-path=<path> Path to SSH key (default: ~/.ssh/id_rsa) diff --git a/setup.py b/setup.py --- a/setup.py +++ b/setup.py @@ -21,1 +21,0 @@ -exec(f.read(), version)
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.69. 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: unitmcp: References a credential file in the home directory (KillerSkills verdict caution 68)
## 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 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/unitmcp/0.1.69 ## Findings with a location - `src/unitmcp/orchestrator/shell.py:613` · References a credential file in the home directory — src/unitmcp/orchestrator/shell.py:613 · References a credential file in the home directory - `src/unitmcp/orchestrator/shell.py:308` · References a credential file in the home directory — src/unitmcp/orchestrator/shell.py:308 · References a credential file in the home directory - `setup.py:21` · Python exec or eval of computed code — setup.py:21 · Python exec or eval of computed code ## 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._
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.