← Home

@luma.gl/gltf

npm Repository
12
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

pessimistressibgreenfelixpalmerbelom88donmccurdykaappchrisgervang

Keywords

webglglsldebug3d

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:glob AI (typosquat): Scoped package @luma.gl/gltf is not a typosquat of glob; Levenshtein match is a false positive. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped package @luma.gl/gltf is not a typosquat of got; Levenshtein match is a false positive. ai
phantom-deps phantom-dep:@loaders.gl/core AI (phantom-deps): @loaders.gl/core is a declared dependency used in config/build files; stable false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
9.3.3 4 / 0
9.3.2 4 / 0
9.3.1 4 / 0
9.3.0 4 / 0
9.2.6 4 / 0
9.2.5 4 / 0
9.2.4 4 / 0
9.2.3 4 / 0
9.2.2 4 / 0
9.2.1 4 / 0
9.2.0 4 / 0
9.1.10 3 / 0

v9.3.3

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.

v9.3.2

1 finding
LOW No provenance attestation provenance

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

v9.3.1

1 finding
LOW No provenance attestation provenance

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

v9.3.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.

v9.2.6

1 finding
LOW No provenance attestation provenance

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

v9.2.5

1 finding
LOW No provenance attestation provenance

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

v9.2.4

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.

v9.2.3

1 finding
LOW No provenance attestation provenance

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

v9.2.2

1 finding
LOW No provenance attestation provenance

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

v9.2.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.

v9.2.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.

v9.1.10

1 finding
LOW No provenance attestation provenance

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