← resq-mcp@1.2.2

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 nixos.org: not declared and not needed for the documented job.

Diff · removes 7 caught lines

Download .patch
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -43,1 +43,0 @@
-<summary>VS Code</summary> A pre-configured [`.vscode/mcp.json`](.vscode/mcp.json) is included in this repo — just open the project and the server is available.
@@ -69,1 +68,0 @@
-<summary>Claude Desktop</summary> Add to your `claude_desktop_config.json` ([MCP install guide](https://modelcontextprotocol.io/quickstart/user)): ```json { "mc
@@ -127,1 +125,0 @@
-<summary>Docker</summary> Run the server as a container in SSE mode: ```json { "mcpServers": { "resq": { "command": "docker", "args": [ "run", "-i", "--rm", "--
@@ -183,1 +180,0 @@
-<summary>Local development</summary> ```bash git clone https://github.com/resq-software/pypi.git cd mcp uv sync uv run resq-mcp ```
diff --git a/CHANGELOG.md b/CHANGELOG.md
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -291,1 +291,0 @@
-documentation including README, AGENTS.md, and CLAUDE.md - Add environment variable validation on
@@ -460,1 +459,0 @@
-- Update .github/workflows/ci.yml with pytest --cov and Codecov upload - Add CLAUDE.md + AGENTS.md
@@ -461,1 +459,0 @@
-agent guide - Add agent-sync.sh to keep AGENTS.md and CLAUDE.md in sync

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.2.2. 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: resq-mcp: Contacted nixos.org: 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.8.1) and scored it **BLOCKED 39/100**. Summary: sends data to nixos.org.

- Contacted nixos.org: not declared and not needed for the documented job.

Full trace and findings: https://killerskills.ai/skills/pypi/resq-mcp/1.2.2

## Findings with a location
- `README.md:183` · Collapsed <details> block carrying instructions — README.md:183 · Collapsed <details> block carrying instructions
- `README.md:69` · Collapsed <details> block carrying instructions — README.md:69 · Collapsed <details> block carrying instructions
- `README.md:43` · Collapsed <details> block carrying instructions — README.md:43 · Collapsed <details> block carrying instructions
- `README.md:127` · Collapsed <details> block carrying instructions — README.md:127 · Collapsed <details> block carrying instructions
- `CHANGELOG.md:291` · Instructs the agent to modify its persistent memory or instruction files — CHANGELOG.md:291 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `CHANGELOG.md:461` · Instructs the agent to modify its persistent memory or instruction files — CHANGELOG.md:461 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `CHANGELOG.md:460` · Instructs the agent to modify its persistent memory or instruction files — CHANGELOG.md:460 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

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