@nocobase/cli-v1@2.2.9
<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-aiSource inspection found no malicious behavior. The flagged credential transfer targets the package registry selected by configuration, with the NocoBase registry as the default, and the shell commands are tied to explicit e2e commands.
Decision evidence
public snapshot- package.json points to the CLI entrypoints and declares no lifecycle scripts.
- The commercial package download command is explicitly invoked; it uses the NocoBase registry by default and returns when credentials are absent or downloads are disabled.
- The login request sends credentials to the configured registry; the default registry is pkg.nocobase.com.
- The license credentials are read from the local license-key file after it is found.
- The e2e process and its shell commands are activated through explicit e2e subcommands.
- The flagged plugin removal is limited to four named NocoBase plugins during environment initialization; the development command also forwards to the app development command when core packages are absent.
Source & flagged code
7 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.9.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.9 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.