@reason-machines/cli-win32-arm64@0.2.534
⚠ Under reviewReason CLI native binary for win32-arm64
AI Security Review
scanned 8h ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged JavaScript shows loopback proxy behavior rather than a confirmed attack. The required native executable’s behavior remains materially unresolved, so manual review is appropriate.
Decision evidence
public snapshot- The inspected manifest identifies a Windows ARM64 CLI binary package and contains no lifecycle scripts.
- The flagged JavaScript includes a local proxy backend bound to loopback.
- The verified offline analysis identifies bin/reason.exe by hash, but its bounded embedded-source windows cannot establish the executable’s full behavior.
- The manifest lists the package’s source repository and homepage.
- The inspected manifest has no install lifecycle hook.
- The inspected proxy code uses loopback addresses; this does not establish malicious network behavior.
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.534.
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.534 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.