@reason-machines/cli-win32-arm64@0.2.437
⚠ Under reviewReason CLI native binary for win32-arm64
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest and required runtime location do not establish an attack, but the bundled executable is a native entrypoint whose available analysis is explicitly incomplete. Manual review is warranted because its behavior remains unresolved.
Decision evidence
public snapshot- The manifest identifies a Windows ARM64 CLI package and declares no lifecycle scripts or JavaScript entrypoint.
- The required runtime location lists project configuration and agent-directory paths, but that excerpt alone does not establish harmful configuration changes.
- The host-generated analysis of bin/reason.exe contains bounded embedded-source windows and states that it cannot establish full executable behavior or rule out other behavior.
- The inspected manifest presents this as a platform-specific native CLI package, consistent with its bundled executable.
- No concrete attack behavior was established in the inspected source.
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.437.
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.437 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.