@prefactor/cli@0.6.0
Prefactor command-line interface
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe reviewed behavior matches a Prefactor CLI: authentication and API calls use the selected service, while installation and updates require explicit commands. The hostname and platform are sent as login metadata during that user-invoked flow.
Decision evidence
public snapshot- The manifest exposes a CLI binary and library entry points, with no install lifecycle script.
- Install and update are explicit CLI commands; the updater downloads releases from the project’s GitHub releases and verifies their SHA-256 checksum.
- Authenticated API clients use a selected profile or PREFACTOR_API_TOKEN with its configured base URL.
- The login command sends client version, platform, and hostname to the selected service’s login endpoint only when the user runs `prefactor login`.
- No automatic credential collection, unrelated data transfer, or unrequested account action was identified.
- The explicit login flow includes the machine hostname and platform in its request metadata.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/install/platform.jsView on unpkg · L1Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
dist/bin/cli.cjsView on unpkg · L495Findings
Affected versions and remediation
This report applies to @prefactor/cli@0.6.0.
See all versions of @prefactor/cli for other recorded verdicts.
- Review the evidence and your use of @prefactor/cli@0.6.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.