@nocobase/cli-v1@2.2.5
<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 flagged process, network, and dynamic-code patterns are tied to CLI package management, explicit E2E setup, version lookup, and development configuration. The inspected source does not establish an attack or unauthorized credential disclosure.
Decision evidence
public snapshot- The manifest identifies CLI entrypoints and lists @nocobase/cli, rather than this package, as a dependency.
- The package login sends credentials to the configured package registry and stores its returned token.
- The download command requires supplied credentials and defaults to the NocoBase package service.
- Playwright dependency installation is behind an explicit E2E subcommand.
- The version helper uses npm output to obtain app-server versions; inspected source does not show arbitrary payload execution.
- The development command uses a configurable CDN and defaults its proxy target to a local address.
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.5.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.5 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.