← fittest-mcp@0.1.0

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

Evidence

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

Diff · removes 5 caught lines

Download .patch
diff --git a/deck/gen.py b/deck/gen.py
--- a/deck/gen.py
+++ b/deck/gen.py
@@ -809,1 +809,0 @@
-"href": "https://fonts.googleapis.com/css2?family=Instrument+Serif:ital@0;1&display=swap"},
@@ -810,1 +809,0 @@
-"geist": {"family": "Geist", "href": "https://fonts.googleapis.com/css2?family=Geist:[email protected]&display=swap"},
@@ -812,1 +810,0 @@
-"href": "https://fonts.googleapis.com/css2?family=Geist+Mono:wght@400;500&display=swap"}},
diff --git a/deck/preview.py b/deck/preview.py
--- a/deck/preview.py
+++ b/deck/preview.py
@@ -14,1 +14,0 @@
-<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Instrument+Serif:ital@0;1&family=Geist:[email protected]&family=Geist+Mono:wght@400;500&display=swap">
diff --git a/deploy/deploy.sh b/deploy/deploy.sh
--- a/deploy/deploy.sh
+++ b/deploy/deploy.sh
@@ -8,1 +8,0 @@
-KEY=${KEY:-$HOME/.ssh/id_rsa}

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.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: fittest-mcp: URL with embedded credentials (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/glama/fittest-mcp/0.1.0

## Findings with a location
- `deck/gen.py:809` · URL with embedded credentials — deck/gen.py:809 · URL with embedded credentials — may be phishing or credential leaking
- `deck/preview.py:14` · URL with embedded credentials — deck/preview.py:14 · URL with embedded credentials — may be phishing or credential leaking
- `deck/gen.py:810` · URL with embedded credentials — deck/gen.py:810 · URL with embedded credentials — may be phishing or credential leaking
- `deck/gen.py:812` · URL with embedded credentials — deck/gen.py:812 · URL with embedded credentials — may be phishing or credential leaking
- `deploy/deploy.sh:8` · References a credential file in the home directory — deploy/deploy.sh:8 · References a credential file in the home directory

## Proposed change
The attached patch removes the 5 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._
# or from a terminal, under your own account:
gh repo fork Pavel-Tk/fittest --clone && cd fittest
curl -s https://killerskills.ai/skills/glama/fittest-mcp/0.1.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.1.0 && git commit -am "fittest-mcp: URL with embedded credentials"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/fittest-mcp/0.1.0/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.