@nocobase/cli-v1@2.2.18
<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 install lifecycle hook, and the flagged process execution is reached through explicit CLI commands. Package credentials go to the configured package registry for authentication; the inspected source does not establish an unrelated recipient or concrete attack.
Decision evidence
public snapshot- package.json exposes CLI entrypoints and has no install lifecycle hook; the inspected manifest depends on @nocobase/cli, not this package.
- The package download command runs only when explicitly invoked, honors DISABLE_PKG_DOWNLOAD, and requires credentials before logging in to its configured package registry.
- Credentials are sent to the configured registry’s login endpoint for package downloads; source shows no separate credential recipient.
- E2E and development commands launch project test and development tools when requested.
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.18.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.18 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.