@nocobase/cli-v1@2.2.16
<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 and flagged source files show no install-time hook or concrete attack behavior. The network and subprocess operations are tied to user-invoked product commands and their intended workflow.
Decision evidence
public snapshot- The manifest declares the CLI entrypoints and no lifecycle scripts.
- The package command sends credentials to its configured registry; the default registry is the NocoBase package service, and access keys are read only within that command.
- The end-to-end test command runs build and Playwright steps as part of an explicit CLI action.
- The development command starts only when the user invokes dev; its subprocess helper uses the supplied command and arguments.
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.16.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.16 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.