@nocobase/cli-v1@2.2.27
<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 script, and reviewed process execution is tied to user-invoked CLI workflows. The credential path is for NocoBase plugin access and defaults to the NocoBase package service; no concrete attack behavior was identified.
Decision evidence
public snapshot- The manifest identifies CLI entrypoints and contains no install lifecycle script.
- The plugin download command defaults to the NocoBase package service, accepts its configured credentials, and uses that service for login.
- Playwright code generation runs from the explicit e2e codegen command and uses the configured application URL.
- The development command forwards the caller's CLI arguments to the application development command.
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.27.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.27 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.