codeplay-common@4.5.1
Common build scripts and files
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package has a guarded, package-owned agent-instruction update path that runs through a build command installed by its lifecycle hook. This leaves a concrete agent configuration risk, but the inspected source does not establish a lifecycle-time control-surface write or another block-level attack.
Decision evidence
public snapshot- The manifest runs cleanup and file synchronization automatically during preinstall and postinstall.
- Postinstall copies package files into the consumer project and rewrites its build command to run a copied build script.
- That build script automatically synchronizes agent instructions when run.
- The sync replaces the project’s AGENTS directory and writes AGENTS.md from a downloaded archive.
- Agent instruction updates are skipped when the required local files are present and current.
- The agent synchronization code checks archive paths before writing staged 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 · L7Findings
Affected versions and remediation
This report applies to codeplay-common@4.5.1.
See all versions of codeplay-common for other recorded verdicts.
- Review the evidence and your use of codeplay-common@4.5.1 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.