codeplay-common@4.9.9
Common build scripts and files
AI Security Review
scanned 13h ago · by lpm-firewall-aiThe source establishes package-owned agent-instruction updates that can replace project-level agent configuration during a build. Because the update is build-triggered and no malicious content is established, this warrants a warning rather than a publish block.
Decision evidence
public snapshot- The package runs cleanup and project setup scripts automatically during installation.
- Its setup script installs a build command that runs the package’s build script.
- Both build-script versions target the consumer project’s AGENTS.md and AGENTS directory, and call the instruction sync during the build.
- The sync checks for a newer instruction version and downloads its archive from htmlcodeplay.com.
- When an update is available, the script replaces the AGENTS directory and writes the downloaded AGENTS.md and support files into the project root.
- The agent-file update runs when the consumer invokes the build command, rather than directly in the npm lifecycle hook.
- The update requires a newer remote version; the download host is associated with the package’s Codeplay product.
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.9.
See all versions of codeplay-common for other recorded verdicts.
- Review the evidence and your use of codeplay-common@4.9.9 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.