← pi-skill-tauri-django-react@0.2.3

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 1 caught line

Download .patch
diff --git a/skills/tauri-django-react/scripts/validate.py b/skills/tauri-django-react/scripts/validate.py
--- a/skills/tauri-django-react/scripts/validate.py
+++ b/skills/tauri-django-react/scripts/validate.py
@@ -1252,1 +1252,0 @@
-("GITHUB_TOKEN", "release workflow uses GITHUB_TOKEN for publishing", "Pass secrets.GITHUB_TOKEN to the release publishing step"),

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.3. 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: pi-skill-tauri-django-react: Credential pass-through configuration (KillerSkills verdict caution 77)

## What the honeypot observed
KillerSkills ran **[email protected]** 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/npm/pi-skill-tauri-django-react/0.2.3

## Findings with a location
- `skills/tauri-django-react/scripts/validate.py:1252` · Credential pass-through configuration — skills/tauri-django-react/scripts/validate.py:1252 · Credential pass-through configuration — agent relays sensitive credentials

## Proposed change
The attached patch removes the 1 line 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 Firstp1ck/pi-coding-agent-forge --clone && cd pi-coding-agent-forge
curl -s https://killerskills.ai/skills/npm/pi-skill-tauri-django-react/0.2.3/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.2.3 && git commit -am "pi-skill-tauri-django-react: Credential pass-through configuration"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/pi-skill-tauri-django-react/0.2.3/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.