@nocobase/cli-v1@2.2.7
<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 install-time hook or concrete attack behavior. The credential flow targets the configured package registry, defaulting to NocoBase’s package service, while flagged shell behavior is tied to user-invoked CLI workflows.
Decision evidence
public snapshot- The manifest exposes CLI entrypoints, depends on the distinct @nocobase/cli package, and contains no lifecycle hooks.
- Package downloads are an explicit CLI operation; credentials are supplied through package environment settings or read from an environment-validated license key.
- The package login sends those credentials to the configured package registry, whose default is the NocoBase package service.
- The flagged e2e shell helpers run from explicit e2e commands.
- The added dev command forwards to app-dev or starts development processes and watches the plugin directory.
- The binary initializes the CLI, and the main module exports utility functions.
- The exported downloadPro helper delegates to the `nocobase pkg download-pro` CLI command.
Source & flagged code
7 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.7.
See all versions of @nocobase/cli-v1 for other recorded verdicts.
- Review the evidence and your use of @nocobase/cli-v1@2.2.7 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.