@slabui/cli@0.4.0
The SlabUI CLI: add, update and compare items from versioned component registries
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe manifest has no install lifecycle scripts, and the flagged process and network capabilities align with the CLI’s stated purpose of managing components and their dependencies. The inspected code shows no unrelated credential collection or concealed automatic execution.
Decision evidence
public snapshot- The manifest declares no lifecycle scripts and exposes a library entry point plus the `slabui` CLI.
- The library client fetches registry data using a supplied registry URL and optional SlabUI token.
- CLI update checks are limited to interactive, non-CI runs and can be disabled with `SLABUI_NO_UPDATE_CHECK=1`.
- The package reads and writes a SlabUI credentials file and uses network requests for registry access and sign-in, which match its stated component-registry purpose.
- The CLI includes child-process support for installing npm dependencies declared by registry items.
Source & flagged code
6 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @slabui/cli@0.4.0.
See all versions of @slabui/cli for other recorded verdicts.
- Review the evidence and your use of @slabui/cli@0.4.0 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.