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. 58 · Caution

Evidence

Read ~/.npmrc in the decoy home directory.

Diff · removes 6 caught lines

Download .patch

diff --git a/lib/claude-integration.js b/lib/claude-integration.js
--- a/lib/claude-integration.js
+++ b/lib/claude-integration.js
@@ -45,1 +45,0 @@
-For your own Claude Code directives, edit CLAUDE.md instead. -->
@@ -76,1 +75,0 @@
-Customized content is preserved. Add personal Claude Code rules in CLAUDE.md.
diff --git a/bin/memtrace.js b/bin/memtrace.js
--- a/bin/memtrace.js
+++ b/bin/memtrace.js
@@ -136,1 +136,0 @@
-"  install    write the Memtrace routing directive into the project's CLAUDE.md\n" +
diff --git a/install.js b/install.js
--- a/install.js
+++ b/install.js
@@ -522,1 +522,0 @@
-//    - add a breadcrumb block to ~/.claude/CLAUDE.md if it exists
diff --git a/lib/project-directive.js b/lib/project-directive.js
--- a/lib/project-directive.js
+++ b/lib/project-directive.js
@@ -80,1 +80,0 @@
-* Add or refresh the Memtrace directive in a project CLAUDE.md.
@@ -162,1 +161,0 @@
-* Write the directive into `<dir>/CLAUDE.md`, creating the file if needed.

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.2.17. 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: memtrace: Read ~/.npmrc in the decoy home directory (KillerSkills verdict caution 58)

## 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 58/100**. Summary: reads credential files.

- Read ~/.npmrc in the decoy home directory.

Full trace and findings: https://killerskills.ai/skills/npm/memtrace/1.2.17

## Findings with a location
- `lib/claude-integration.js:76` · Instructs the agent to modify its persistent memory or instruction files — lib/claude-integration.js:76 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file · informational: not an instruction file · informationa
- `bin/memtrace.js:136` · Instructs the agent to modify its persistent memory or instruction files — bin/memtrace.js:136 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file · informational: not an instruction file · informational: not an
- `install.js:522` · Instructs the agent to modify its persistent memory or instruction files — install.js:522 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file · informational: not an instruction file · informational: not an inst
- `lib/project-directive.js:80` · Instructs the agent to modify its persistent memory or instruction files — lib/project-directive.js:80 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file · informational: not an instruction file · informational
- `lib/claude-integration.js:45` · Instructs the agent to modify its persistent memory or instruction files — lib/claude-integration.js:45 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file · informational: not an instruction file · informationa
- `lib/project-directive.js:162` · Instructs the agent to modify its persistent memory or instruction files — lib/project-directive.js:162 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file · informational: not an instruction file · informationa

## Proposed change
The attached patch removes the 6 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._

Open the issue on GitHub (syncable-dev/memtrace-public)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork syncable-dev/memtrace-public --clone && cd memtrace-public
curl -s https://killerskills.ai/skills/npm/memtrace/1.2.17/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.2.17 && git commit -am "memtrace: Read ~/.npmrc in the decoy home directory"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/memtrace/1.2.17/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.