@nocobase/cli-v1@2.2.25
<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 lifecycle scripts, and inspected process execution is tied to explicit CLI commands. Credential login uses credentials supplied to the package command and defaults to the NocoBase package service, with no unrelated recipient or covert transfer identified.
Decision evidence
public snapshot- The manifest exposes the CLI and has no install lifecycle hook.
- The package command sends credentials to the NocoBase package service; it requires supplied credentials and defaults to pkg.nocobase.com.
- E2E process execution is activated by the explicit e2e test command.
- The dynamic function parses version data returned by an npm query.
- Development subprocesses are activated by the explicit dev command.
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.25.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.25 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.