codeplay-common@4.8.5
Common build scripts and files
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe install hooks perform broad project-file cleanup and copy operations, while a later generated build command can replace agent instructions without an affirmative consent check. This establishes a concrete capability and residual configuration risk, but not an install-hook agent-control hijack.
Decision evidence
public snapshot- The package runs preinstall cleanup and postinstall project synchronization during installation.
- The preinstall script recursively removes selected project directories and generated files.
- The postinstall script copies package files into the consumer project and changes its package manifest.
- The generated build command runs a script that automatically synchronizes agent instructions.
- That build script downloads a newer archive from the package vendor and replaces root agent-instruction files without an affirmative consent check.
- The agent-instruction synchronization runs from the generated build command, not directly from either npm lifecycle hook.
- The setup is version-gated and stages archive contents before replacing the agent-instruction files.
Source & flagged code
10 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references child process execution.
files/generate-ai-promo-video.jsView on unpkg · L17Findings
Affected versions and remediation
This report applies to codeplay-common@4.8.5.
See all versions of codeplay-common for other recorded verdicts.
- Review the evidence and your use of codeplay-common@4.8.5 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.