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

Evidence

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

Diff · removes 2 caught lines

Download .patch

diff --git a/tests/run_tests.sh b/tests/run_tests.sh
--- a/tests/run_tests.sh
+++ b/tests/run_tests.sh
@@ -44,1 +44,0 @@
-run IPJUDGE_TEST_SITE="http://localhost:$PORT/s/good" https_proxy="http://alice:[email protected]:$PORT/p?token=QUERYSECRET"
@@ -132,1 +131,0 @@
-printf '{"env":{"HTTPS_PROXY":"http://zed:[email protected]:1"},"apiKeyHelper":"sk-ant-LEAKME"}\n' > "$SANDBOX/.claude/settings.json"

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of r1. 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: ipjudge: URL with embedded credentials (KillerSkills verdict caution 70)

## What the honeypot observed
KillerSkills ran **ipjudge@r1** 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/glama/ipjudge/r1

## Findings with a location
- `tests/run_tests.sh:44` · URL with embedded credentials — tests/run_tests.sh:44 · URL with embedded credentials — may be phishing or credential leaking
- `tests/run_tests.sh:132` · URL with embedded credentials — tests/run_tests.sh:132 · URL with embedded credentials — may be phishing or credential leaking

## Proposed change
The attached patch removes the 2 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 (ipjudge/ipjudge)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork ipjudge/ipjudge --clone && cd ipjudge
curl -s https://killerskills.ai/skills/glama/ipjudge/r1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/r1 && git commit -am "ipjudge: URL with embedded credentials"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/ipjudge/r1/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.