codeplay-common@4.5.0
Common build scripts and files
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe automatic preinstall hook performs destructive deletion in the consumer project, including recursive removal of a whole directory. This concrete install-time behavior supports blocking the package.
Decision evidence
public snapshot- package.json automatically runs scripts/uninstall.js during preinstall and scripts/sync-files.js during postinstall.
- The preinstall script recursively deletes the consumer project's buildCodeplay directory, including its contents, and also removes a splashxml directory.
- The same preinstall script deletes root-level files matching several build and plugin filename patterns.
- The postinstall script copies package files into the project root and writes modified contents to the consumer's package.json.
- The cleanup targets named build and plugin artifacts, which is consistent with removing files from an earlier package setup, but it also removes the entire buildCodeplay directory recursively.
Source & flagged code
11 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 · L7Source file is highly similar to a previously finalized malicious package; route for source-aware review.
Findings
Affected versions and remediation
This report applies to codeplay-common@4.5.0.
See all versions of codeplay-common for other recorded verdicts.
- Avoid installing codeplay-common@4.5.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.