@nocobase/cli-v1@2.2.3
<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 has no install lifecycle hook, and the credential flow is activated by an explicit download command and targets the NocoBase package service by default. The flagged process execution supports user-invoked CLI functionality; inspected source did not establish malicious behavior.
Decision evidence
public snapshot- package.json declares CLI entrypoints and dependencies but no lifecycle scripts.
- The package-service login is part of the explicit `pkg download-pro` command and defaults to the NocoBase package service.
- Login credentials come from a stored license key or package-service environment variables and are sent to that service's login endpoint.
- E2E build and Playwright commands run only through explicit CLI actions.
- The dev command forwards arguments to the NocoBase app CLI; the shell helper is general command execution.
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.3.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.3 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.