codeplay-common@4.8.8
Common build scripts and files
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe lifecycle hooks perform project cleanup and synchronization, while the potentially risky agent-instruction replacement occurs when the consumer runs the configured build. Because that build-triggered update changes project agent guidance without a separate confirmation, warn about the capability; the inspected source does not prove an active attack.
Decision evidence
public snapshot- The preinstall and postinstall hooks run project cleanup and file synchronization.
- Synchronization adds a build command that runs the package’s build helper; that helper updates agent instructions during the build.
- The helper fetches versioned instructions from htmlcodeplay.com and replaces the project’s AGENTS.md and AGENTS directory.
- The archive checks reject absolute paths and entries containing .. before staging files.
- The agent-instruction update is reached through the project build command, not directly through either npm lifecycle hook.
- The source validates archive paths before writing staged files; the inspected code does not establish malicious payload behavior.
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.8.8.
See all versions of codeplay-common for other recorded verdicts.
- Review the evidence and your use of codeplay-common@4.8.8 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.