@nocobase/cli-v1
<video width="100%" controls> <source src="https://github.com/user-attachments/assets/4d11a87b-00e2-48f3-9bf7-389d21072d13" type="video/mp4"> </video>
This report shows the evidence for @nocobase/cli-v1@2.2.15. 1 of 39 known versions is blocked or flagged. The newest version, 2.2.30, is flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe startup deletion is an unguarded destructive side effect on the consumer’s plugin storage. Although compatibility cleanup is possible, the inspected source provides no condition or explanation that resolves that risk.
Decision evidence
public snapshot- The executable calls environment initialization before parsing CLI arguments.
- Initialization sets the plugin storage location under the configured storage root.
- Initialization recursively removes four named plugin directories without checking the selected command.
- The deletion is limited to four named NocoBase plugin directories, which could reflect compatibility cleanup, but the source does not guard it or explain that purpose.
Source & flagged code
6 flagged · loading sourcePackage source references child process execution.
src/commands/e2e.jsView on unpkg · L11Package source invokes a package manager install command at runtime.
src/commands/e2e.jsView on unpkg · L123Findings
Affected versions and remediation
This report applies to @nocobase/cli-v1@2.2.15.
The versions list below shows the verdict for each recorded version.
- Avoid installing @nocobase/cli-v1@2.2.15. 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.