← reversecore-mcp@3.1.0

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

Evidence

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

Diff · removes 5 caught lines

Download .patch
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -767,1 +767,0 @@
-<summary>🍎 macOS</summary> ```json { "mcpServers": { "reversecore": { "command": "docker", "args": [ "run", "-i", "--rm", "-v", "/Users/YOUR_USERNAME/samples:/
@@ -789,1 +788,0 @@
-<summary>🐧 Linux</summary> ```json { "mcpServers": { "reversecore": { "command": "docker", "args": [ "run", "-i", "--rm", "-v", "/home/YOUR_USERNAME/samples:/a
@@ -811,1 +809,0 @@
-<summary>🪟 Windows</summary> ```json { "mcpServers": { "reversecore": { "command": "docker", "args": [ "run", "-i", "--rm", "-v", "C:/samples:/app/workspace", 
@@ -1661,1 +1658,0 @@
-<summary><b>Timeout error (RCMCP-E002 / RCMCP-E200)</b></summary> Analysis exceeded the configured timeout. **Solution:** Increase the timeout: ```bash export R
@@ -1692,1 +1688,0 @@
-<summary><b>Docker container won't start on Apple Silicon</b></summary> Make sure you're using the ARM64 profile: ```bash docker compose --profile arm64 up -d `

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 3.1.0. 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: reversecore-mcp: Collapsed <details> block carrying instructions (KillerSkills verdict caution 71)

## 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 **CAUTION 71/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/reversecore-mcp/3.1.0

## Findings with a location
- `README.md:789` · Collapsed <details> block carrying instructions — README.md:789 · Collapsed <details> block carrying instructions
- `README.md:767` · Collapsed <details> block carrying instructions — README.md:767 · Collapsed <details> block carrying instructions
- `README.md:1661` · Collapsed <details> block carrying instructions — README.md:1661 · Collapsed <details> block carrying instructions
- `README.md:1692` · Collapsed <details> block carrying instructions — README.md:1692 · Collapsed <details> block carrying instructions
- `README.md:811` · Collapsed <details> block carrying instructions — README.md:811 · Collapsed <details> block carrying instructions

## Proposed change
The attached patch removes the 5 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 sjkim1127/Reversecore_MCP --clone && cd Reversecore_MCP
curl -s https://killerskills.ai/skills/pypi/reversecore-mcp/3.1.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/3.1.0 && git commit -am "reversecore-mcp: Collapsed <details> block carrying instructions"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/reversecore-mcp/3.1.0/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.