@reason-machines/cli-win32-arm64@0.2.412
⚠ Under reviewReason CLI native binary for win32-arm64
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest and flagged JavaScript location do not establish malicious behavior. The required native executable has only limited offline analysis, which cannot rule out material behavior, so manual review is warranted.
Decision evidence
public snapshot- The inspected manifest identifies a Windows ARM64 CLI binary package and contains no install hook or JavaScript entrypoint.
- The sandbox runtime lists MCP and agent configuration paths among its protected-path rules; the exact flagged match is part of that path list.
- The native executable is an 86 MB PE, and the bounded offline analysis says its sampled embedded source cannot establish loader reachability or rule out other native behavior.
- The manifest has no install lifecycle scripts, and the flagged JavaScript match is sandbox path-policy code rather than a credential transfer or agent configuration write.
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.412.
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.412 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.