@nocobase/cli-v1@2.2.19
<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 the inspected subprocess and package-authentication behavior is tied to explicit CLI use and the NocoBase package service. The flagged cleanup is limited to four named plugin directories, so the inspected source supports a clean verdict.
Decision evidence
public snapshot- package.json exposes the CLI entrypoints and depends on the matching @nocobase/cli release.
- The package login sends credentials to the configured package service; its default is the NocoBase package host, and the command requires package credentials before login.
- The E2E install and shell operations are reached through an explicit `e2e test` command.
- The `dev` command is user-invoked, and its subprocess helper runs commands passed by CLI code.
- Startup cleanup is limited to four named NocoBase plugin directories.
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.19.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.19 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.