← passioncode@0.2.80

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. 39 · Blocked

Evidence

  • Contacted analytics.passioncode.ai: not declared and not needed for the documented job.

Diff · removes 3 caught lines

Download .patch
diff --git a/payload/plugins/fabric-agent-adapter/skills/building-fabric-services/scripts/fabric_a2a.py b/payload/plugins/fabric-agent-adapter/skills/building-fabric-services/scripts/fabric_a2a.py
--- a/payload/plugins/fabric-agent-adapter/skills/building-fabric-services/scripts/fabric_a2a.py
+++ b/payload/plugins/fabric-agent-adapter/skills/building-fabric-services/scripts/fabric_a2a.py
@@ -35,1 +35,0 @@
-"

   ")
diff --git a/payload/plugins/passioncode/hooks/repo-rules.js b/payload/plugins/passioncode/hooks/repo-rules.js
--- a/payload/plugins/passioncode/hooks/repo-rules.js
+++ b/payload/plugins/passioncode/hooks/repo-rules.js
@@ -5,1 +5,0 @@
-* wiki.passioncode.ai/knowledge) and the repository's AGENTS.md before its first edit, and after
@@ -48,1 +47,0 @@
-…ad the knowledge base (${KNOWLEDGE} or ${KNOWLEDGE_WEB}), then this repository's AGENTS.md, before the first edit; work by Fabric principle 10, a free agent takes the next task (a wait goes on …

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.80. 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: passioncode: Contacted analytics.passioncode.ai: not declared and not needed for the documented job (KillerSkills verdict blocked 39)

## 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 **BLOCKED 39/100**. Summary: sends data to analytics.passioncode.ai.

- Contacted analytics.passioncode.ai: not declared and not needed for the documented job.

Full trace and findings: https://killerskills.ai/skills/npm/passioncode/0.2.80

## Findings with a location
- `payload/plugins/fabric-agent-adapter/skills/building-fabric-services/scripts/fabric_a2a.py:35` · Hidden zero-width characters detected — payload/plugins/fabric-agent-adapter/skills/building-fabric-services/scripts/fabric_a2a.py:35 · Hidden zero-width characters detected — may conceal content
- `payload/plugins/passioncode/hooks/repo-rules.js:5` · Instructs the agent to modify its persistent memory or instruction files — payload/plugins/passioncode/hooks/repo-rules.js:5 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `payload/plugins/passioncode/hooks/repo-rules.js:48` · Instructs the agent to modify its persistent memory or instruction files — payload/plugins/passioncode/hooks/repo-rules.js:48 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

## Proposed change
The attached patch removes the 3 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 passioncode-ai/passioncode --clone && cd passioncode
curl -s https://killerskills.ai/skills/npm/passioncode/0.2.80/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.2.80 && git commit -am "passioncode: Contacted analytics.passioncode.ai: not declared and not needed for the documented job"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/passioncode/0.2.80/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.