@blazeinstall/hyperglob@1.0.5
A multi-threaded, AST-aware, zero-copy file discovery engine designed to replace legacy globbing for AI agents, monorepos, and high-performance developer tooling.
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource confirms an automatic install hook that adds the package’s MCP server to multiple agent configuration surfaces without consent. This is an unconsented install-time AI-agent control-surface change.
Decision evidence
public snapshot- package.json runs scripts/install.js automatically after installation.
- The installer writes changed agent configuration files without prompting for consent.
- The installer adds the package’s MCP server to global and project agent settings when no existing entry is present.
- It also enables a global Kilo Code entry and adds entries to global and project Cursor settings.
- mcp.js exposes file-query tools to agents that load the server.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs scripts/install.js automatically after installation.
package.jsonView on unpkg · L57Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @blazeinstall/hyperglob@1.0.5.
See all versions of @blazeinstall/hyperglob for other recorded verdicts.
- Avoid installing @blazeinstall/hyperglob@1.0.5. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.