@minecraft/common
See full documentation for this module here:
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from rlanda to mc-npm within the @minecraft org; mc-npm has 32 approved packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mc-npm is the new org-level publisher for @minecraft packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @minecraft/common is an official Microsoft/Mojang Minecraft scripting API package. Minimal metadata, no deps, and tiny payload are characteristic of this entire namespace and not spam indicators. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has 27 approved versions with no rejections; lack of Sigstore provenance is consistent across all versions of this package and is not a risk for this established Microsoft-affiliated publisher. | ai |
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.