Propose a patch

Evidence

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

diff --git a/dist/ship/publish.js b/dist/ship/publish.js
--- a/dist/ship/publish.js
+++ b/dist/ship/publish.js
@@ -76,1 +76,0 @@
-* dir passed as --userconfig (which also keeps any persistent ~/.npmrc token
diff --git a/dist/lockfiles.js b/dist/lockfiles.js
--- a/dist/lockfiles.js
+++ b/dist/lockfiles.js
@@ -352,1 +352,0 @@
-const text = raw.replace(/^/, "");

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

## 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 65/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/shipsecure-mcp/0.1.1

## Findings with a location
- `dist/ship/publish.js:76` · References a credential file in the home directory — dist/ship/publish.js:76 · References a credential file in the home directory
- `dist/lockfiles.js:352` · Hidden zero-width characters detected — dist/lockfiles.js:352 · Hidden zero-width characters detected — may conceal content

## 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._