@reason-machines/cli-win32-arm64@0.2.403
⚠ Under reviewReason CLI native binary for win32-arm64
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no lifecycle hook, and the inspected runtime excerpt does not establish an attack. The required native executable analysis is explicitly limited and cannot resolve code reachability or other behavior, so manual review is warranted.
Decision evidence
public snapshot- The manifest identifies a Windows ARM64 native CLI package and contains no lifecycle hook or JavaScript entrypoint.
- The flagged runtime includes .mcp.json among protected paths, but this excerpt does not establish how that protection is activated.
- The native executable analysis contains bounded embedded source candidates for local runtime operations, while explicitly stating that reachability and other native behavior remain unresolved.
- The manifest has no install lifecycle hook, so installation-time execution is not established.
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.403.
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.403 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.