scip-query@0.22.0
Evidence and verification for AI coding agents: map code, reuse concepts, finish migrations, and gate diffs.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle hook is automatic but its shipped entrypoint only logs a message. The remaining flagged primitives are package-aligned CLI and code-analysis functionality, with no concrete malicious chain.
Decision evidence
public snapshot- An automatic postinstall hook is present.
- The postinstall entry only prints an installation message; its imported helpers are not invoked.
- The flagged analysis bundle was inspected; its VM-related code is a garbage-collection helper, not payload execution.
- No self-dependency on scip-query is declared.
- No install-time network request, file mutation, credential collection, or child-process invocation was found.
- The registry request is a one-second, opt-out update check triggered by CLI use, not installation.
Source & flagged code
7 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 unpkgFindings
Affected versions and remediation
This report applies to scip-query@0.22.0.
See all versions of scip-query for other recorded verdicts.
- Review the evidence and your use of scip-query@0.22.0 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.