@reason-machines/cli-linux-x64-musl@0.2.359
⚠ Under reviewReason CLI native binary for linux-x64-musl
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe inspected JavaScript shows local credential discovery and a local-login handover gated by configuration, but does not prove a credential attack. The required native executable analysis is incomplete, so the package cannot be cleared or blocked on the available source evidence.
Decision evidence
public snapshot- The manifest identifies this as a Linux musl native-binary package and contains no lifecycle script in the inspected manifest.
- The CLI source reads credentials from local Claude, Codex, Grok, OpenCode, and Pi locations; a local-login handover is gated by the localLogins setting, though its default and transfer details need further resolution.
- The required native executable is a 99 MB ELF binary; its offline analysis is limited and does not establish loader reachability or rule out other native behavior.
- The inspected CLI source defaults localLogins to true when the setting is omitted, so the handover gate alone does not establish affirmative user consent.
- The inspected source does not establish a concrete credential transfer attack or other malicious behavior.
Source & flagged code
23 flagged · loading sourcePackage source references child process execution.
bin/runtime/srt/sandbox-runtime.mjsView on unpkg · L60A single source file combines environment access, network access, and code or shell execution; review context before blocking.
Findings
Affected versions and remediation
This report applies to @reason-machines/cli-linux-x64-musl@0.2.359.
See all versions of @reason-machines/cli-linux-x64-musl for other recorded verdicts.
- Review the evidence and your use of @reason-machines/cli-linux-x64-musl@0.2.359 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.