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

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 4 caught lines

Download .patch

diff --git a/dist/cjs/mcp/utils.js b/dist/cjs/mcp/utils.js
--- a/dist/cjs/mcp/utils.js
+++ b/dist/cjs/mcp/utils.js
@@ -419,1 +419,0 @@
-* `head $HOME/.ssh/id_rsa` and a symlink pointing out of the tree all pass the command allowlist
diff --git a/dist/esm/mcp/utils.js b/dist/esm/mcp/utils.js
--- a/dist/esm/mcp/utils.js
+++ b/dist/esm/mcp/utils.js
@@ -399,1 +399,0 @@
-* `head $HOME/.ssh/id_rsa` and a symlink pointing out of the tree all pass the command allowlist
diff --git a/bin/init.js b/bin/init.js
--- a/bin/init.js
+++ b/bin/init.js
@@ -305,1 +305,0 @@
-// 1. Write CLAUDE.md in project root
@@ -771,1 +770,0 @@
-// Add AGENTS.md instructions path if supported

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.49.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: lemma: References a credential file in the home directory (KillerSkills verdict caution 77)

## 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 77/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/lemma/1.49.1

## Findings with a location
- `dist/cjs/mcp/utils.js:419` · References a credential file in the home directory — dist/cjs/mcp/utils.js:419 · References a credential file in the home directory
- `dist/esm/mcp/utils.js:399` · References a credential file in the home directory — dist/esm/mcp/utils.js:399 · References a credential file in the home directory
- `bin/init.js:771` · Instructs the agent to modify its persistent memory or instruction files — bin/init.js:771 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `bin/init.js:305` · Instructs the agent to modify its persistent memory or instruction files — bin/init.js:305 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

## Proposed change
The attached patch removes the 4 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 (Nxusbets/lemma)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork Nxusbets/lemma --clone && cd lemma
curl -s https://killerskills.ai/skills/npm/lemma/1.49.1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.49.1 && git commit -am "lemma: References a credential file in the home directory"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/lemma/1.49.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.