← Home

@azure/mcp-linux-arm64

npm Repository Homepage

Azure MCP Server - Model Context Protocol implementation for Azure, for linux on arm64

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

azure-sdkmicrosoft1esmicrosoft-oss-releases

Keywords

azuremcpmodel-context-protocol

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): This package is a platform-specific native binary launcher; child_process is required to spawn the azmcp binary. Expected and safe for this package. ai
semgrep semgrep:child-process-spawn AI (semgrep): spawn() with shell:false is the canonical safe pattern for launching the bundled native binary. Expected behavior for this Microsoft binary wrapper package. ai
bogus-package bogus-package AI (bogus-package): Link-heavy README and no JS deps are expected for a Microsoft platform-specific binary distribution package. Not indicative of spam or phishing. ai

Versions (showing 8 of 8)

Version Deps Published
2.0.2 0 / 0
2.0.1 0 / 0
2.0.0 0 / 0
1.0.4 0 / 0
1.0.3 0 / 0
1.0.2 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.