Propose a patch

Evidence

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

diff --git a/src/pmcp/manifest/manifest.yaml b/src/pmcp/manifest/manifest.yaml
--- a/src/pmcp/manifest/manifest.yaml
+++ b/src/pmcp/manifest/manifest.yaml
@@ -1113,1 +1113,0 @@
-env_instructions: "Uses active kubeconfig (~/.kube/config or KUBECONFIG env var)"
diff --git a/src/pmcp/manifest/npm_resolver.py b/src/pmcp/manifest/npm_resolver.py
--- a/src/pmcp/manifest/npm_resolver.py
+++ b/src/pmcp/manifest/npm_resolver.py
@@ -99,1 +99,0 @@
-# `npx --name foo probe`). `HOME` relocates `~/.npmrc`, so `HOME=/x` with
diff --git a/scripts/pipeline-bootstrap/run.mjs b/scripts/pipeline-bootstrap/run.mjs
--- a/scripts/pipeline-bootstrap/run.mjs
+++ b/scripts/pipeline-bootstrap/run.mjs
@@ -297,1 +297,0 @@
-const cloneUrl = `https://x-access-token:${cloneToken}@github.com/${repository_full_name}.git`;

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

## 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 70/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/pmcp/3.0.3

## Findings with a location
- `src/pmcp/manifest/manifest.yaml:1113` · References a credential file in the home directory — src/pmcp/manifest/manifest.yaml:1113 · References a credential file in the home directory
- `src/pmcp/manifest/npm_resolver.py:99` · Reads credential paths from the home directory — src/pmcp/manifest/npm_resolver.py:99 · Reads credential paths from the home directory
- `scripts/pipeline-bootstrap/run.mjs:297` · URL with embedded credentials — scripts/pipeline-bootstrap/run.mjs:297 · URL with embedded credentials — may be phishing or credential leaking
- `src/pmcp/manifest/npm_resolver.py:99` · References a credential file in the home directory — src/pmcp/manifest/npm_resolver.py:99 · References a credential file in 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._