@m8t-stack/cli@0.2.164
CLI for managing m8t deployments on Azure / Microsoft Agent Foundry
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe inspected source shows package-aligned deployment and companion operations without a concrete malicious chain. The flagged agent integration is a read-only drift check, and gateway credentials are freshly generated rather than copied from an existing service session.
Decision evidence
public snapshot- package.json defines no registry install lifecycle hooks or runtime self-dependency.
- The indicated agent integration locates m8t-architect skill metadata and reads it for a drift check; it does not modify agent configuration.
- Gateway setup generates a fresh bearer rather than forwarding an existing service session credential.
- Azure authentication is sent to management.azure.com when provisioning the gateway connection.
- Companion installation runs through a CLI command and checks package-owned destination boundaries.
Source & flagged code
7 flagged · loading sourceSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/cli.jsView on unpkg · L130Findings
Affected versions and remediation
This report applies to @m8t-stack/cli@0.2.164.
See all versions of @m8t-stack/cli for other recorded verdicts.
- Review the evidence and your use of @m8t-stack/cli@0.2.164 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.