Propose a patch

Evidence

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

diff --git a/dist/guard-pack.js b/dist/guard-pack.js
--- a/dist/guard-pack.js
+++ b/dist/guard-pack.js
@@ -372,1 +372,0 @@
-* Credential files the never-list does not already cover (it has ssh keys, `~/.aws/credentials`, gcloud
diff --git a/dist/ioc/scan.js b/dist/ioc/scan.js
--- a/dist/ioc/scan.js
+++ b/dist/ioc/scan.js
@@ -102,1 +102,0 @@
-out.push(finding(ioc, check, `~/.ssh/authorized_keys line ${line}`));
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -104,1 +104,0 @@
-Gateway section: local MCP gate with listeners, routes, backends, policies, and a dry-run playground

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

## 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 62/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/kya/0.33.6

## Findings with a location
- `dist/guard-pack.js:372` · References a credential file in the home directory — dist/guard-pack.js:372 · References a credential file in the home directory
- `dist/ioc/scan.js:102` · Reads credential paths from the home directory — dist/ioc/scan.js:102 · Reads credential paths from the home directory
- `README.md:104` · Image alt text carrying instructions — README.md:104 · Image alt text carrying instructions
- `dist/guard-pack.js:372` · Reads credential paths from the home directory — dist/guard-pack.js:372 · Reads credential paths from the home directory

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