@reason-machines/cli-darwin-x64@0.2.373
⚠ Under reviewReason CLI native binary for darwin-x64
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe inspected code shows credential collection and a transfer path, but the bounded native analysis does not establish the effective recipient or consent, and does not resolve the full executable. Manual review is needed to determine whether this is the intended session feature or an unsafe disclosure.
Decision evidence
public snapshot- The manifest identifies a Darwin x64 CLI package and has no lifecycle scripts.
- The inspected runtime includes .mcp.json and agent command and agent paths in a path list; the cited excerpt shows no configuration write.
- The native executable analysis contains only bounded embedded source windows and says they cannot establish its full behavior.
- When local login support is unset, the inspected native source enables it by default and starts a handoff when enabled.
- The handoff reads credentials from local coding agent stores and repeatedly submits them through a local subscription call.
- The source identifies a device-authenticated /local-subscription route, but the effective API origin, recipient consent, and the rest of the native executable remain unresolved.
Source & flagged code
6 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-darwin-x64@0.2.373.
See all versions of @reason-machines/cli-darwin-x64 for other recorded verdicts.
- Review the evidence and your use of @reason-machines/cli-darwin-x64@0.2.373 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.