scip-query@0.21.1
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 install lifecycle is transparent and only logs a message. Static inspection found no self-dependency chain, automatic control-surface mutation, credential collection, or payload execution.
Decision evidence
public snapshot- The manifest invokes a postinstall script.
- The postinstall source only prints an installation message; it does not perform file, network, or process actions.
- The high-priority analysis chunk was inspected and contains source-analysis helper logic, not an install payload.
- No self-dependency on scip-query was found.
- The registry request is a runtime update check with a one-second timeout and can be disabled by environment variables.
- Child-process calls support explicit CLI indexer discovery and installation, not automatic postinstall execution.
- Agent and project mutations are exposed as explicit CLI commands, not lifecycle actions.
Source & flagged code
5 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.21.1.
See all versions of scip-query for other recorded verdicts.
- Review the evidence and your use of scip-query@0.21.1 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.