@nocobase/cli-v1@2.2.24
<video width="100%" controls> <source src="https://github.com/user-attachments/assets/4d11a87b-00e2-48f3-9bf7-389d21072d13" type="video/mp4"> </video>
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest defines no lifecycle hook, and inspected network and process execution is tied to explicit CLI commands and package-aligned functionality. The scanner signals do not establish malicious behavior.
Decision evidence
public snapshot- package.json has no lifecycle scripts and points to the CLI entrypoints.
- The package download command sends supplied credentials to the configurable NocoBase package service and requires credentials before proceeding.
- The end-to-end install and process commands run only when the user invokes the corresponding CLI command.
- The flagged dev command forwards to the app-dev command when the project lacks core packages; its file write serves development status reporting.
- The runtime package dependency is @nocobase/cli, not this package name.
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.24.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.24 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.