← shrike-mcp@0.4.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. 69 · 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/shrike/embedding.py b/src/shrike/embedding.py
--- a/src/shrike/embedding.py
+++ b/src/shrike/embedding.py
@@ -105,1 +105,0 @@
-# Raw passthrough token strings (each shlex-split at command-build time).
diff --git a/src/shrike/cli/config.py b/src/shrike/cli/config.py
--- a/src/shrike/cli/config.py
+++ b/src/shrike/cli/config.py
@@ -157,1 +157,0 @@
-"""Passthrough token strings via flag → env → config (flag wins).
diff --git a/docs/audits/audit-55f832d.md b/docs/audits/audit-55f832d.md
--- a/docs/audits/audit-55f832d.md
+++ b/docs/audits/audit-55f832d.md
@@ -221,1 +221,0 @@
-…rip too, or document that they're file-only. (Decided: file-only — documented in CLAUDE.md's "Config file" section. `save_config` does not write `logging.*`.) ### 7.3 [MEDIUM] CLAUDE.md claims "Periodic index save" is done,…

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.4.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: shrike-mcp: Credential pass-through configuration (KillerSkills verdict caution 69)

## 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 69/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/shrike-mcp/0.4.0

## Findings with a location
- `src/shrike/embedding.py:105` · Credential pass-through configuration — src/shrike/embedding.py:105 · Credential pass-through configuration — agent relays sensitive credentials
- `src/shrike/cli/config.py:157` · Credential pass-through configuration — src/shrike/cli/config.py:157 · Credential pass-through configuration — agent relays sensitive credentials
- `docs/audits/audit-55f832d.md:221` · Instructs the agent to modify its persistent memory or instruction files — docs/audits/audit-55f832d.md:221 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

## 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 lathrys-at/shrike --clone && cd shrike
curl -s https://killerskills.ai/skills/pypi/shrike-mcp/0.4.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.4.0 && git commit -am "shrike-mcp: Credential pass-through configuration"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/shrike-mcp/0.4.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.