codeplay-common@4.6.2
Common build scripts and files
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe build setup can replace consumer-project agent instructions with publisher-hosted content, creating a concrete agent-configuration risk. Because the update runs through a user-invoked build command and aligns with the package’s build-tooling role, a warning is appropriate.
Decision evidence
public snapshot- The manifest runs a cleanup script before installation and a file-sync script after installation.
- The postinstall sync copies package files into the consumer project and changes its build command to run codeplayBeforeBuild-6.3.js.
- That build script automatically calls the agent-instruction updater.
- When a newer version is available, the updater downloads an archive from htmlcodeplay.com and replaces the project’s AGENTS.md and AGENTS directory.
- The updater is reached through a user-run build command and checks whether the remote version is newer before replacing the instruction files.
- The package describes itself as providing common build scripts and files, which is consistent with adding build setup.
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.6.2.
See all versions of codeplay-common for other recorded verdicts.
- Review the evidence and your use of codeplay-common@4.6.2 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.