@reason-machines/cli-linux-x64-musl@0.2.396
⚠ Under reviewReason CLI native binary for linux-x64-musl
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe inspected JavaScript shows a gated local-login transfer to the Reason service, with no verified unrelated recipient or concrete attack. The 99.8 MB native executable has only bounded embedded-source analysis that cannot rule out other behavior, so its safety remains unresolved.
Decision evidence
public snapshot- The bounded offline analysis says it cannot establish whether embedded native code is reachable or rule out other native behavior.
- The JavaScript reads saved provider access credentials and sends provider data through the device-proof local-subscription route when localLogins is enabled.
- The local-login setting defaults to enabled when unspecified; the inspected client configuration uses Reason service APIs.
- No concrete malicious behavior was verified in the inspected JavaScript, but the native executable remains unresolved.
- The inspected credential-transfer path is gated by the localLogins setting and uses the Reason service client’s local-subscription route.
- The source inspection did not verify an unrelated credential recipient or a concrete attack.
Source & flagged code
25 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.396.
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.396 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.