@nocobase/cli-v1@2.2.28
<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 default login serves the package’s licensed plugin download function, but a custom registry URL can receive a saved license key without a recipient-specific check. This is a conditional credential exposure risk, so warn rather than block.
Decision evidence
public snapshot- The license access key is read from a local license file and checked against the current environment.
- The package download command accepts a configurable registry URL and can use the saved license access key as login credentials.
- The login request sends those credentials to the configured registry URL without checking that it is the NocoBase service.
- The transfer runs only when the package download command is invoked and credentials are available.
- The default registry URL is the NocoBase package service, where this login supports downloading licensed plugins.
- The package also permits explicit username and password environment variables for the login.
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.28.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.28 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.