@prefactor/cli@0.5.0
Prefactor command-line interface
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe user-triggered login flow sends the machine hostname to Prefactor's service as client information without disclosing that collection. This is an identifying telemetry privacy risk, but the source shows no unrelated collection or credential theft.
Decision evidence
public snapshot- The CLI's login command collects the machine hostname and includes it in client information.
- When login starts, the CLI sends that information in a POST request to the configured Prefactor service's /cli/login/start endpoint.
- The hostname is truncated to 64 characters before it is sent.
- The hostname is sent only during the user-invoked login flow, not on package installation or import.
- The default destination is Prefactor's own service, and login is the CLI's stated purpose.
- No credential theft or unrelated process execution was identified.
Source & flagged code
6 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.5.0.
See all versions of @prefactor/cli for other recorded verdicts.
- Review the evidence and your use of @prefactor/cli@0.5.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.