Propose a patch

Evidence

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

diff --git a/src/mcp_placard/inject/patterns.py b/src/mcp_placard/inject/patterns.py
--- a/src/mcp_placard/inject/patterns.py
+++ b/src/mcp_placard/inject/patterns.py
@@ -611,1 +611,0 @@
-_ZERO_WIDTH = re.compile("[​‌‍‎‏⁠⁡⁢⁣⁤]+")
@@ -791,1 +790,0 @@
-The sensitive-path patterns match a prefix — ``~/.ssh`` out of ``~/.ssh/id_rsa``,
@@ -792,1 +790,0 @@
-``~/.aws`` out of ``~/.aws/credentials`` — so comparing what they matched compares a
@@ -798,1 +795,0 @@
-``~/.aws/credentials`` is naming its own subject; the same parameter pointed at
@@ -799,1 +795,0 @@
-``~/.ssh/id_rsa`` is not. ``config_path`` may name ``~/.config`` and still not be
diff --git a/src/mcp_placard/transport/launch.py b/src/mcp_placard/transport/launch.py
--- a/src/mcp_placard/transport/launch.py
+++ b/src/mcp_placard/transport/launch.py
@@ -13,1 +13,0 @@
-the real ``HOME`` would hand the server ``~/.npmrc``, ``~/.docker/config.json``,
diff --git a/src/mcp_placard/inject/surface.py b/src/mcp_placard/inject/surface.py
--- a/src/mcp_placard/inject/surface.py
+++ b/src/mcp_placard/inject/surface.py
@@ -125,1 +125,0 @@
-one at ``file:///var/log/app.log`` may not mention ``~/.ssh/id_rsa``. Empty means

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

## 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 68/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/mcp-placard/0.7.0

## Findings with a location
- `src/mcp_placard/inject/patterns.py:791` · References a credential file in the home directory — src/mcp_placard/inject/patterns.py:791 · References a credential file in the home directory
- `src/mcp_placard/inject/patterns.py:611` · Hidden zero-width characters detected — src/mcp_placard/inject/patterns.py:611 · Hidden zero-width characters detected — may conceal content
- `src/mcp_placard/inject/patterns.py:799` · References a credential file in the home directory — src/mcp_placard/inject/patterns.py:799 · References a credential file in the home directory
- `src/mcp_placard/inject/patterns.py:798` · References a credential file in the home directory — src/mcp_placard/inject/patterns.py:798 · References a credential file in the home directory
- `src/mcp_placard/inject/patterns.py:792` · References a credential file in the home directory — src/mcp_placard/inject/patterns.py:792 · References a credential file in the home directory
- `src/mcp_placard/transport/launch.py:13` · References a credential file in the home directory — src/mcp_placard/transport/launch.py:13 · References a credential file in the home directory
- `src/mcp_placard/inject/surface.py:125` · References a credential file in the home directory — src/mcp_placard/inject/surface.py:125 · References a credential file in the home directory

## Proposed change
The attached patch removes the 7 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._