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

Evidence

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

Diff · removes 6 caught lines

Download .patch

diff --git a/.claude/commands/release.md b/.claude/commands/release.md
--- a/.claude/commands/release.md
+++ b/.claude/commands/release.md
@@ -125,1 +125,0 @@
-`uv publish` reads credentials from `~/.pypirc` natively. Do NOT pass tokens via command-line arguments (they leak into the process list).
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -104,1 +104,0 @@
-<summary>From Source</summary> ```bash git clone https://github.com/sprine/ontario-data-mcp cd ontario-data-mcp uv sync uv run ontario-data-mcp ``` To connect f
@@ -175,1 +174,0 @@
-<summary><b>Querying</b> (4 tools)</summary> | Tool | Description | |------|-------------| | `query_resource` | Query a resource via CKAN Datastore API (remote)
@@ -198,1 +196,0 @@
-<summary><b>Geospatial</b> (3 tools)</summary> | Tool | Description | |------|-------------| | `load_geodata` | Cache a geospatial resource (SHP, KML, GeoJSON) 
diff --git a/site/index.html b/site/index.html
--- a/site/index.html
+++ b/site/index.html
@@ -541,1 +541,0 @@
-<summary> <div class="tool-card-head"> <span class="tool-card-name">Querying</span> <span class="tool-card-count">4 tools</span> </div> <div class="tool-card-de
@@ -561,1 +560,0 @@
-<summary> <div class="tool-card-head"> <span class="tool-card-name">Geospatial</span> <span class="tool-card-count">3 tools</span> </div> <div class="tool-card-

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.2. 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: ontario-data-mcp: Credential pass-through configuration (KillerSkills verdict caution 74)

## 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 74/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/ontario-data-mcp/0.2.2

## Findings with a location
- `.claude/commands/release.md:125` · Credential pass-through configuration — .claude/commands/release.md:125 · Credential pass-through configuration — agent relays sensitive credentials
- `README.md:175` · Collapsed <details> block carrying instructions — README.md:175 · Collapsed <details> block carrying instructions
- `site/index.html:541` · Collapsed <details> block carrying instructions — site/index.html:541 · Collapsed <details> block carrying instructions · informational: not an instruction file
- `README.md:198` · Collapsed <details> block carrying instructions — README.md:198 · Collapsed <details> block carrying instructions
- `README.md:104` · Collapsed <details> block carrying instructions — README.md:104 · Collapsed <details> block carrying instructions
- `site/index.html:561` · Collapsed <details> block carrying instructions — site/index.html:561 · Collapsed <details> block carrying instructions · informational: not an instruction file

## 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 (sprine/ontario-data-mcp)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork sprine/ontario-data-mcp --clone && cd ontario-data-mcp
curl -s https://killerskills.ai/skills/pypi/ontario-data-mcp/0.2.2/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.2.2 && git commit -am "ontario-data-mcp: Credential pass-through configuration"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/ontario-data-mcp/0.2.2/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.