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

Evidence

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

Diff

No finding carries a file and line, so there is no mechanical diff; the issue body below carries the evidence and the fix is a declaration or a removal the maintainer chooses.

Issue / PR body

Title: igsight-mcp: behavior the sandbox flagged (KillerSkills verdict caution 76)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.5) and scored it **CAUTION 76/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/igsight-mcp/1.3.0

## Findings with a location
- No finding carries a file and line; the evidence above comes from the run itself.

## Proposed change
Declare the behavior if it is intended (hosts under `permissions.network`, a line in the README), or remove it. The next crawl re-scores the new version automatically.

## 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._

Open the issue on GitHub (vinihuge/igsight-mcp)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork vinihuge/igsight-mcp --clone && cd igsight-mcp
curl -s https://killerskills.ai/skills/pypi/igsight-mcp/1.3.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.3.0 && git commit -am "igsight-mcp: behavior the sandbox flagged"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/igsight-mcp/1.3.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.