codeplay-common@4.9.4
Common build scripts and files
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe source shows unconditional lifecycle-time deletion of project directories, creating a concrete destructive risk, though the surrounding copy and build-script changes are consistent with the package’s stated tooling role. The separate agent-instructions replacement is called from a later build script, not the install hooks.
Decision evidence
public snapshot- The preinstall hook runs project cleanup, including recursive deletion of the project’s buildCodeplay and splashxml directories.
- The postinstall hook copies bundled files into the project root and rewrites build scripts in package.json.
- A later build script can replace the project’s AGENTS directory and AGENTS.md with downloaded instructions; this is separate from the npm install hooks.
- The cleanup and file copying are consistent with the package’s build-tooling purpose, but the preinstall deletion is unconditional.
- The agent-instructions update runs from the build script, not directly from either lifecycle hook.
Source & flagged code
12 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.9.4.
See all versions of codeplay-common for other recorded verdicts.
- Review the evidence and your use of codeplay-common@4.9.4 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.