@reason-machines/cli-linux-arm64@0.2.342
⚠ Under reviewReason CLI native binary for linux-arm64
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe inspected JavaScript shows disclosed, setting-controlled forwarding of local provider access tokens to the Reason service, but does not establish an unrelated recipient or malicious use. The shipped native executable remains materially unresolved, so this source review cannot support a clean verdict.
Decision evidence
public snapshot- The package manifest contains no lifecycle scripts and identifies the package as a Linux ARM64 native binary.
- The shipped executable is a 102,869,136-byte ELF; its offline analysis covers bounded embedded-source windows and says those windows cannot establish reachability or rule out other native behavior.
- The JavaScript reads local provider access tokens and submits them through the Reason client’s local-subscription operation when local logins are enabled; the executable’s embedded help says this feature is on by default.
- The manifest describes a platform-specific Reason CLI binary, and the inspected token-submission path uses the Reason client.
- The embedded help describes the local-login behavior and says an API key turns it off. No source inspected establishes an unrelated credential recipient or malicious use.
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-arm64@0.2.342.
See all versions of @reason-machines/cli-linux-arm64 for other recorded verdicts.
- Review the evidence and your use of @reason-machines/cli-linux-arm64@0.2.342 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.