@chem-x/starter-kit@26.9.16-668
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe inspected agent configuration changes are available through explicit setup commands, so the source supports a warning for agent capability rather than an install-time control hijack. The manifest's postinstall target is absent from this package snapshot, and the inspected sources show no concrete attack behavior.
Decision evidence
public snapshot- The manifest defines a postinstall command that points to scripts/postinstall.mjs; that file is absent from the package snapshot.
- The installer can append a directive to an existing AGENTS.md file.
- The installer exposes agent and MCP setup through explicit CLI commands.
- The MCP installer writes configuration under .cursor/mcp.json; its test invokes that installer directly.
- The package snapshot contains no scripts/postinstall.mjs, so the declared postinstall command has no corresponding source file here.
- The reviewed agent configuration changes are reached through installer commands, not shown as automatic import-time behavior.
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 source references child process execution.
cli/audit-preflight-git.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @chem-x/starter-kit@26.9.16-668.
See all versions of @chem-x/starter-kit for other recorded verdicts.
- Review the evidence and your use of @chem-x/starter-kit@26.9.16-668 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.