← krusch-stack@1.3.1

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 .patch
diff --git a/src/installer/ide-config.js b/src/installer/ide-config.js
--- a/src/installer/ide-config.js
+++ b/src/installer/ide-config.js
@@ -242,1 +242,0 @@
-* Safely write/merge IDE MCP configurations and scaffold `.agent/AGENTS.md` if missing.
diff --git a/docs/guides/adding-memory-to-cursor-and-claude-code.md b/docs/guides/adding-memory-to-cursor-and-claude-code.md
--- a/docs/guides/adding-memory-to-cursor-and-claude-code.md
+++ b/docs/guides/adding-memory-to-cursor-and-claude-code.md
@@ -11,1 +11,0 @@
-…of a project, then fail in three predictable ways: 1. **Silent Rule Rot**: You write *"Always validate Stripe webhooks in `src/api/stripe.ts`"* in `CLAUDE.md`. Two months later, someone refactors that handler or changes its signature. Th…

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.3.1. 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: krusch-stack: Instructs the agent to modify its persistent memory or instruction files (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/npm/krusch-stack/1.3.1

## Findings with a location
- `src/installer/ide-config.js:242` · Instructs the agent to modify its persistent memory or instruction files — src/installer/ide-config.js:242 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `docs/guides/adding-memory-to-cursor-and-claude-code.md:11` · Instructs the agent to modify its persistent memory or instruction files — docs/guides/adding-memory-to-cursor-and-claude-code.md:11 · Instructs the agent to modify its persistent memory or instruction files · 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 kruschdev/krusch-stack --clone && cd krusch-stack
curl -s https://killerskills.ai/skills/npm/krusch-stack/1.3.1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.3.1 && git commit -am "krusch-stack: Instructs the agent to modify its persistent memory or instruction files"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/krusch-stack/1.3.1/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.