codeplay-common@4.6.0
Common build scripts and files
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe build script performs automatic, publisher-hosted updates to project agent instructions, leaving a concrete configuration risk. The package’s lifecycle hooks do not invoke that sync, so the evidence supports a warning rather than a block.
Decision evidence
public snapshot- The postinstall hook copies package files into the consumer project and updates its package.json scripts.
- Running the packaged build script fetches newer agent instructions from htmlcodeplay.com and replaces the project’s AGENTS.md and AGENTS directory when the remote version is newer.
- The build script calls this agent-instruction sync as part of its build flow.
- The agent-instruction sync is in a build script; the package’s install hooks run scripts/sync-files.js and scripts/uninstall.js instead.
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.0.
See all versions of codeplay-common for other recorded verdicts.
- Review the evidence and your use of codeplay-common@4.6.0 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.