@reason-machines/cli-win32-arm64@0.2.394
⚠ Under reviewReason CLI native binary for win32-arm64
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no lifecycle hook, and the inspected runtime location does not prove harmful agent configuration behavior. The required executable analysis is bounded and leaves activation and credential handling unresolved, so manual review is appropriate.
Decision evidence
public snapshot- package.json identifies a Windows ARM64 package containing platform binaries and defines no lifecycle hook.
- The required runtime location defines paths related to MCP and Claude configuration, but this excerpt does not establish a configuration write or its caller.
- The executable’s bounded embedded-source analysis contains a helper that reads provider API-key values; the helper’s activation and recipient are not established.
- The host analysis explicitly says its bounded source windows cannot prove executable reachability or exclude other native behavior.
- No package install hook or confirmed credential transfer appears in the inspected evidence.
- The inspected runtime excerpt alone does not establish an agent configuration mutation.
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-win32-arm64@0.2.394.
See all versions of @reason-machines/cli-win32-arm64 for other recorded verdicts.
- Review the evidence and your use of @reason-machines/cli-win32-arm64@0.2.394 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.