mtech-ai-local-runner@0.1.86
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 3d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the CLI’s configuration changes are behind an explicit integrations install command. The README’s flagged wording describes project status rather than attempting to direct the review.
Decision evidence
public snapshot- The manifest contains no preinstall, install or postinstall hook.
- The CLI runs its main command only when invoked directly.
- Agent integrations are reached through the explicit `integrations` command, and hook installation occurs only for the `install` action.
- The README says Codex hooks are appended after backing up the file and require the user to trust them before they run.
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.86.
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.86 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.