@m8t-stack/cli@0.2.12
CLI for managing m8t-stack deployments on Azure / Microsoft Agent Foundry
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection shows suspicious primitives are expected for this CLI's documented Azure/GitHub/Foundry management functions and are activated by explicit commands. No lifecycle execution, credential harvesting, covert endpoint, persistence, destructive payload, or unconsented AI-agent control-surface mutation was found.
Decision evidence
public snapshot- package.json has no install/postinstall hook; prepublishOnly only runs pnpm build for publishers.
- dist/cli.js entrypoint registers Clipanion commands and runs only when the CLI is invoked.
- child_process usage is limited to user-invoked az, gh, git, open/start/xdg-open, and brain-eval commands.
- Network calls are aligned with documented Azure, GitHub, GHCR, OpenAI SDK, and user-configured gateway operations.
- Secret reads/writes are for Azure Key Vault GitHub App auth and local m8t config/credential files documented in README.md.
- AI-agent instruction/tool mutations occur in explicit brain/a2a commands for Foundry agent management, not lifecycle or hidden execution.
Source & flagged code
2 flagged · loading sourceSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/cli.jsView on unpkg · L19321Findings
Affected versions and remediation
This report applies to @m8t-stack/cli@0.2.12.
See all versions of @m8t-stack/cli for other recorded verdicts.
- Review the evidence and your use of @m8t-stack/cli@0.2.12 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.