@nocobase/cli-v1@2.2.20
<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-aiSource inspection found no lifecycle hook or concrete attack behavior. Credential login is part of the explicitly invoked plugin-download command and defaults to the NocoBase package service; process execution is tied to explicit E2E or development commands.
Decision evidence
public snapshot- The manifest exposes a command-line entrypoint and depends on the matching NocoBase CLI release; it declares no install lifecycle hook.
- The plugin-download command runs only when explicitly invoked, defaults to the NocoBase package service, and requires configured credentials before logging in.
- The login request sends those credentials to the package manager's configured service URL.
- E2E install, build, and Playwright subprocesses are inside explicitly invoked E2E commands.
- The development command and bootstrap initialize the CLI; the version helper evaluates output from an npm version query, and no package source caller was found.
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.20.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.20 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.