hscrape@0.2.33
Evo Headless Scraper CLI. Installs the `hscrape` binary for your platform plus the evo-scraper skill for Claude Code.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe automatic installation and replacement of a Claude Code skill creates a concrete, limited agent-extension lifecycle risk. The inspected source does not establish a broader control-surface attack, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- The package runs the skill installer automatically from its npm postinstall hook.
- The installer targets a named skill directory in the user's Claude Code skills folder.
- When the version stamp does not match, the installer recursively removes that directory and copies in the bundled skill.
- The hscrape launcher also runs the installer when the CLI is invoked.
- The bundled file identifies itself as an Evo scraper skill for Claude Code.
- A matching version stamp makes the installer leave the existing skill directory and its local edits alone.
- The inspected installer targets one named skill directory; it does not modify broad Claude Code settings.
- The bundled skill describes Evo scraper workflows, and the inspected source does not establish credential transfer or remote code execution.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package runs the skill installer automatically from its npm postinstall hook.
package.jsonView on unpkg · L13Source fingerprint signature matches a known malicious package signature; route for source-aware review.
Findings
Affected versions and remediation
This report applies to hscrape@0.2.33.
See all versions of hscrape for other recorded verdicts.
- Review the evidence and your use of hscrape@0.2.33 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.