@reason-machines/cli-linux-x64-musl@0.2.545
Reason CLI native binary for linux-x64-musl
AI Security Review
scanned 5h ago · by lpm-firewall-aiThe inspected source shows default-on transfer of existing third-party access tokens to Reason's service. This is concrete credential disclosure to a publisher-selected recipient, so the package should be blocked.
Decision evidence
public snapshot- Hash-verified offline analysis of the native CLI contains the credential collection and handover code; the analysis notes that embedded-source reachability is bounded.
- The CLI reads existing provider login credentials from local stores, including OAuth access tokens.
- When enabled, the worker sends collected login data through the Reason local-subscription request.
- The worker invokes that handover at startup when local logins are enabled; the configuration defaults to enabled, and the CLI describes it as on by default.
- The Reason API endpoints are package-owned service hosts, while the transferred credentials belong to other providers.
- The CLI presents local-login support as a session feature and says it transfers current access tokens rather than refresh tokens; that description does not provide a separate affirmative choice to send those credentials to Reason.
Source & flagged code
24 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.545.
See all versions of @reason-machines/cli-linux-x64-musl for other recorded verdicts.
- Avoid installing @reason-machines/cli-linux-x64-musl@0.2.545. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.