← Home

@minecraft/server

npm

Contains many types related to manipulating a Minecraft world, including entities, blocks, dimensions, and more.

28
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

mammerladarknavirlandamc-npm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:semver AI (typosquat): @minecraft/server is an official Microsoft/Mojang Minecraft scripting API package with 1310 days history and 502 versions; string similarity to 'semver' is purely coincidental and not a typosquat. ai
bogus-package bogus-package AI (bogus-package): @minecraft/server is an official Microsoft/Mojang package; sparse metadata (no repo URL, no keywords, minimal README) is a consistent pattern across the entire @minecraft/* namespace, not a spam indicator. ai
provenance no-provenance AI (provenance): Microsoft's @minecraft/* packages consistently publish without Sigstore provenance attestation; this is a stable characteristic of the namespace. ai

Versions (showing 28 of 28)

Version Deps Published
2.7.0 0 / 0
2.6.0 0 / 0
2.5.0 0 / 0
2.4.0 0 / 0
2.3.0 0 / 0
2.2.0 0 / 0
2.1.0 1 / 0
2.0.0 1 / 0
1.19.0 1 / 0
1.18.0 1 / 0
1.17.0 1 / 0
1.16.0 1 / 0
1.15.0 1 / 0
1.14.0 1 / 0
1.13.0 1 / 0
1.12.0 1 / 0
1.11.0 1 / 0
1.10.0 1 / 0
1.9.0 1 / 0
1.8.0 1 / 0
1.7.0 1 / 0
1.6.0 1 / 0
1.5.0 0 / 0
1.4.0 0 / 0
1.3.0 0 / 0
1.2.0 0 / 0
1.1.0 0 / 0
1.0.0 0 / 0

v2.7.0

1 finding
INFO No provenance attestation provenance

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

v2.6.0

1 finding
LOW No provenance attestation provenance

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

v2.5.0

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.0

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.19.0

1 finding
LOW No provenance attestation provenance

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

v1.18.0

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

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

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

1 finding
LOW No provenance attestation provenance

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

v1.14.0

1 finding
LOW No provenance attestation provenance

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

v1.13.0

1 finding
LOW No provenance attestation provenance

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

v1.12.0

1 finding
LOW No provenance attestation provenance

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

v1.11.0

1 finding
LOW No provenance attestation provenance

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

v1.10.0

1 finding
LOW No provenance attestation provenance

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

v1.9.0

1 finding
INFO No provenance attestation provenance

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

v1.8.0

1 finding
INFO No provenance attestation provenance

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

v1.7.0

1 finding
INFO No provenance attestation provenance

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

v1.6.0

1 finding
INFO No provenance attestation provenance

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

v1.5.0

1 finding
INFO No provenance attestation provenance

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

v1.4.0

2 findings
HIGH Publisher changed: darknavi → rlanda (on 2023-09-19) provenance

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

INFO No provenance attestation provenance

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

v1.3.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@minecraft/server' is 1 edit(s) away from popular package 'semver'.

INFO No provenance attestation provenance

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

v1.2.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@minecraft/server' is 1 edit(s) away from popular package 'semver'.

INFO No provenance attestation provenance

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

v1.1.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@minecraft/server' is 1 edit(s) away from popular package 'semver'.

INFO No provenance attestation provenance

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

v1.0.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@minecraft/server' is 1 edit(s) away from popular package 'semver'.

INFO No provenance attestation provenance

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