@blazeinstall/hyperglob@0.4.2
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe lifecycle network access is used to obtain this package’s platform-specific native binding from its project release endpoint. Inspected MCP operations perform client-requested local searches, with no source evidence of credential collection, unrelated data transfer, or other concrete attack behavior.
Decision evidence
public snapshot- package.json runs scripts/install.js after installation.
- The installer checks for a platform-specific native binding and downloads it from this package’s GitHub Releases URL.
- The MCP runtime returns results from file-search operations, including paths and metadata.
- The dependent-file operation returns the local query result.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpackage.json runs scripts/install.js after installation.
package.jsonView on unpkg · L57The installer checks for a platform-specific native binding and downloads it from this package’s GitHub Releases URL.
scripts/install.jsView on unpkg · L18The installer checks for a platform-specific native binding and downloads it from this package’s GitHub Releases URL.
scripts/install.jsView on unpkg · L16Findings
Affected versions and remediation
This report applies to @blazeinstall/hyperglob@0.4.2.
See all versions of @blazeinstall/hyperglob for other recorded verdicts.
- Review the evidence and your use of @blazeinstall/hyperglob@0.4.2 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.