@azure/mcp-win32-x64 MIT 9 versions

@azure/mcp-win32-x64

npm Repository Homepage

Azure MCP Server - Model Context Protocol implementation for Azure, for win32 on x64

9

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.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:child-process-import	AI (semgrep): child_process is used to launch the bundled azmcp.exe binary — standard pattern for platform-specific binary wrapper packages. Not arbitrary command execution.	ai	2026/04/25
semgrep	semgrep:child-process-spawn	AI (semgrep): spawn() launches the bundled .exe with shell:false — safe binary launcher pattern, not user-controlled input execution.	ai	2026/04/25
bogus-package	bogus-package	AI (bogus-package): Platform-specific binary distribution package from Microsoft; link-heavy README and no npm deps are expected for this package type.	ai	2026/04/25

Versions (showing 9 of 9)

Version	Deps	Published
2.0.3	0 / 0	2026-06-08
2.0.2	0 / 0	2026-04-25
2.0.1	0 / 0	2026-04-14
2.0.0	0 / 0	2026-04-10
1.0.4	0 / 0	2026-03-19
1.0.3	0 / 0	2026-03-18
1.0.2	0 / 0	2026-03-06
1.0.1	0 / 0	2025-11-26
1.0.0	0 / 0	2025-10-28

v2.0.3

1 finding

LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.