mtech-ai-local-runner@0.1.82
D6 owner revision `fbc30fbe-cac9-45d1-9eff-bccec6ee6a54` selects a separate Gateway-initiated P2 verification budget: at most 1,500 weighted minutes per UTC calendar month and one active verification per workspace. This does not cap or certify the entire
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe daemon automatically sends diagnostic telemetry with runner-linked heartbeats, and the package documentation does not disclose this reporting or show a way to disable it. The inspected payload is limited to status and runtime details, so this warrants a warning rather than a block.
Decision evidence
public snapshot- Starting the daemon starts a self-check monitor that runs checks automatically and repeats them every six hours.
- The report includes local tool and hook status, Node kind and version, and failure reasons.
- The daemon adds self-checks and a device fingerprint to its heartbeat payload.
- The default destination is the AI Gateway endpoint.
- The reported fields are bounded diagnostics rather than credentials, prompts, or project contents.
- The manifest shows build and explicit CLI scripts, with no install lifecycle hook.
Source & flagged code
5 flaggedPackage text addresses the security reviewer or scanner and tries to influence the review outcome.
README.mdView on unpkgPackage source references dynamic require/import behavior.
dist/src/adapters/codex/pre-model-gate.jsView on unpkg · L31Findings
Affected versions and remediation
This report applies to mtech-ai-local-runner@0.1.82.
See all versions of mtech-ai-local-runner for other recorded verdicts.
- Review the evidence and your use of mtech-ai-local-runner@0.1.82 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.