@minecraft/vanilla-data No license 40 versions

@minecraft/vanilla-data

npm

40

Versions

—

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

mammerladarknavirlandamc-npm

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 individual (rlanda) to team account (mc-npm); both Microsoft-affiliated.	ai	2026/06/04
maintainer-change	maintainer-added	AI (maintainer-change): mc-npm is the new org-level publisher for this Microsoft-owned scope.	ai	2026/06/04
bogus-package	bogus-package	AI (bogus-package): Official Minecraft types package from Microsoft; no deps/repo/keywords is expected for this data-only types package.	ai	2026/05/05

Versions (showing 40 of 40)

Version	Deps	Published
1.26.21	0 / 0	2026-05-14
1.26.20	0 / 0	2026-05-05
1.26.13	0 / 0	2026-04-06
1.26.12	0 / 0	2026-03-31
1.26.10	0 / 0	2026-03-24
1.26.2	0 / 0	2026-02-25
1.26.1	0 / 0	2026-02-19
1.26.0	0 / 0	2026-02-10
1.21.131	0 / 0	2025-12-16
1.21.130	0 / 0	2025-12-09
1.21.124	0 / 0	2025-11-21
1.21.123	0 / 0	2025-11-13
1.21.120	0 / 0	2025-10-28
1.21.114	0 / 0	2025-10-16
1.21.113	0 / 0	2025-10-09
1.21.111	0 / 0	2025-09-30
1.21.101	0 / 0	2025-08-13
1.21.100	0 / 0	2025-08-06
1.21.93	0 / 0	2025-07-03
1.21.90	0 / 0	2025-06-17
1.21.81	0 / 0	2025-05-14
1.21.80	0 / 0	2025-05-06
1.21.70	0 / 0	2025-03-25
1.21.62	0 / 0	2025-02-25
1.21.61	0 / 0	2025-02-19
1.21.60	0 / 0	2025-02-11
1.21.50	0 / 0	2024-12-03
1.21.44	0 / 0	2024-10-31
1.21.43	0 / 0	2024-10-25
1.21.41	0 / 0	2024-10-22
1.21.40	0 / 0	2024-10-22
1.21.31	0 / 0	2024-09-30
1.21.30	0 / 0	2024-09-17
1.21.23	0 / 0	2024-09-03
1.21.22	0 / 0	2024-08-26
1.21.20	0 / 0	2024-08-13
1.21.3	0 / 0	2024-07-15
1.21.2	0 / 0	2024-07-09
1.21.1	0 / 0	2024-06-20
1.21.0	0 / 0	2024-06-13

v1.26.21

1 finding

LOW No provenance attestation provenance

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

v1.26.20

1 finding

LOW No provenance attestation provenance

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

v1.26.13

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.26.12

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.26.10

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.26.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.

v1.26.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.

v1.26.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.21.131

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.21.130

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.21.124

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.21.123

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.21.120

1 finding

LOW No provenance attestation provenance

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

v1.21.114

1 finding

LOW No provenance attestation provenance

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

v1.21.113

1 finding

LOW No provenance attestation provenance

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

v1.21.111

1 finding

LOW No provenance attestation provenance

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

v1.21.101

1 finding

LOW No provenance attestation provenance

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

v1.21.100

1 finding

LOW No provenance attestation provenance

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

v1.21.93

1 finding

LOW No provenance attestation provenance

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

v1.21.90

1 finding

LOW No provenance attestation provenance

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

v1.21.81

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.21.80

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.21.70

2 findings

HIGH Publisher changed: rlanda → mc-npm (on 2025-03-25) provenance

This version was published by a different npm account than previous versions on 2025-03-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.21.62

2 findings

HIGH Publisher changed: rlanda → mc-npm (on 2025-02-25) provenance

This version was published by a different npm account than previous versions on 2025-02-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.21.61

2 findings

HIGH Publisher changed: rlanda → mc-npm (on 2025-02-19) provenance

This version was published by a different npm account than previous versions on 2025-02-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.21.60

2 findings

HIGH Publisher changed: rlanda → mc-npm (on 2025-02-11) provenance

This version was published by a different npm account than previous versions on 2025-02-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.21.50

2 findings

HIGH Publisher changed: rlanda → mc-npm (on 2024-12-03) provenance

This version was published by a different npm account than previous versions on 2024-12-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.21.44

1 finding

LOW No provenance attestation provenance

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

v1.21.43

1 finding

LOW No provenance attestation provenance

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

v1.21.41

1 finding

LOW No provenance attestation provenance

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

v1.21.40

1 finding

LOW No provenance attestation provenance

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

v1.21.31

1 finding

LOW No provenance attestation provenance

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

v1.21.30

1 finding

LOW No provenance attestation provenance

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

v1.21.23

1 finding

LOW No provenance attestation provenance

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

v1.21.22

1 finding

LOW No provenance attestation provenance

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

v1.21.20

1 finding

LOW No provenance attestation provenance

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

v1.21.3

1 finding

LOW No provenance attestation provenance

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

v1.21.2

1 finding

LOW No provenance attestation provenance

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

v1.21.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.

v1.21.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.