@nocobase/cli-v1@2.2.22
<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 package manifest has no lifecycle scripts, and the flagged shell, process, and network behavior belongs to explicit CLI operations. The credential flow reads a local license key and sends it to the NocoBase package service by default; inspected source shows no concrete attack behavior.
Decision evidence
public snapshot- package.json declares CLI entrypoints and dependencies, with no lifecycle scripts in the manifest.
- The package download command defaults to NocoBase’s package service and is activated through the explicit `pkg download-pro` CLI command.
- License access keys are read from the local license file and sent to the configured package service for login.
- `e2e` commands run app, build, test, and Playwright setup operations when invoked.
- `dev` runs the local app development stack and forwards to the NocoBase CLI.
- The shared process runner uses a shell, but the inspected callers use it for explicit CLI development and test operations.
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.22.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.22 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.