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. 77 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/python/src/thinkerwave/client.py b/python/src/thinkerwave/client.py
--- a/python/src/thinkerwave/client.py
+++ b/python/src/thinkerwave/client.py
@@ -57,1 +57,0 @@
-raise InvalidKeyError("invalid_key", "No API key. Set THINKERWAVE_API_KEY or pass api_key=… "
diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md
--- a/.github/ISSUE_TEMPLATE/bug.md
+++ b/.github/ISSUE_TEMPLATE/bug.md
@@ -17,1 +17,0 @@
-Do not paste your API key.
diff --git a/.github/ISSUE_TEMPLATE/wrong_answer.md b/.github/ISSUE_TEMPLATE/wrong_answer.md
--- a/.github/ISSUE_TEMPLATE/wrong_answer.md
+++ b/.github/ISSUE_TEMPLATE/wrong_answer.md
@@ -15,1 +15,0 @@
-Do not paste your API key. Don't paste confidential details from your problem — the run id is enough for us to look it up.
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -13,1 +13,0 @@
-A real two-round ThinkerWave run in the terminal
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: thinkerwave: Credential pass-through configuration (KillerSkills verdict caution 77)
## What the honeypot observed
KillerSkills ran **thinkerwave@r1** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 77/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/thinkerwave/r1
## Findings with a location
- `python/src/thinkerwave/client.py:57` · Credential pass-through configuration — python/src/thinkerwave/client.py:57 · Credential pass-through configuration — agent relays sensitive credentials
- `.github/ISSUE_TEMPLATE/bug.md:17` · Prompting user to enter sensitive credentials — .github/ISSUE_TEMPLATE/bug.md:17 · Prompting user to enter sensitive credentials — social engineering
- `.github/ISSUE_TEMPLATE/wrong_answer.md:15` · Prompting user to enter sensitive credentials — .github/ISSUE_TEMPLATE/wrong_answer.md:15 · Prompting user to enter sensitive credentials — social engineering
- `README.md:13` · Image alt text carrying instructions — README.md:13 · Image alt text carrying instructions
## Proposed change
The attached patch removes the 4 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 thinkerwave-ai/thinkerwave --clone && cd thinkerwave curl -s https://killerskills.ai/skills/glama/thinkerwave/r1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/r1 && git commit -am "thinkerwave: Credential pass-through configuration" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/thinkerwave/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.