@nocobase/cli-v1@2.2.23
<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 hook, and the reviewed network and process behavior is associated with explicit CLI commands. The scanner signals did not establish malicious behavior.
Decision evidence
public snapshot- package.json declares CLI entrypoints and no install lifecycle hook.
- The package login posts supplied credentials to the configured package service; the default is pkg.nocobase.com.
- The e2e build and test commands run only when a user invokes the e2e test command.
- The dev command forwards user arguments to the NocoBase CLI.
- The dynamic Function parses version output from an npm command; no separate attack behavior was identified.
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.23.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.23 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.