@prefactor/cli@0.4.1
Prefactor command-line interface
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged process and network behavior belongs to the CLI’s explicit managed-binary install/update workflow, which downloads from the project’s GitHub releases and verifies checksums. The library entry point exports CLI functions without invoking them at import time, and no malicious behavior was found.
Decision evidence
public snapshot- The manifest defines a CLI binary and a separate library entry point.
- The library entry point exports runCli but does not invoke it automatically.
- Binary installation is registered as an explicit CLI command.
- The installer fetches release assets from the project’s GitHub releases and checks them against a SHA256 manifest.
- The CLI can download, extract, and run its own managed binary during an explicit install or update command.
- The package includes API commands that authenticate with the user’s Prefactor account when invoked.
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.4.1.
See all versions of @prefactor/cli for other recorded verdicts.
- Review the evidence and your use of @prefactor/cli@0.4.1 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.