← Home

@cesium/engine

npm Repository Homepage
9
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

cesiumgsadminggetzlukemckinstryjjspacejjhembdadamcesiummzschwartz5

Keywords

3Dwebglgeospatialmapglobe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): WASM decoders (draco/basis/zip/splats) are legit deps of a 3D globe engine. ai
dependencies unvetted-dep:@cesium/wasm-splats AI (dependencies): First-party @cesium-scoped dependency. ai
semgrep semgrep:new-function-constructor AI (semgrep): Used in KTX2 transcoding worker for named function creation; standard pattern in compiled/bundled worker code. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get in a Proxy handler trap is idiomatic JS; not obfuscation. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require in geometry worker is a documented worker-module loading pattern for CesiumJS. ai
provenance no-provenance AI (provenance): Established Cesium org package; lack of provenance is common and not a risk signal here. ai

Versions (showing 9 of 9)

Version Deps Published
26.1.0 21 / 0
26.0.0 21 / 0
25.0.0 21 / 0
24.0.0 21 / 0
23.0.1 21 / 0
23.0.0 21 / 0
22.3.0 21 / 0
22.2.0 21 / 0
22.1.0 21 / 0

v26.1.0

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: lukemckinstry → ggetz (on 2026-07-01, known maintainer) provenance

This version was published by a different npm account (ggetz) than the most recent previously approved version (lukemckinstry) on 2026-07-01, but ggetz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v24.0.0

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • Source/ThirdParty/basis_transcoder.wasm • Source/ThirdParty/draco_decoder.wasm • Source/ThirdParty/wasm_splats_bg.wasm • Source/ThirdParty/zip-module.wasm

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.

v23.0.1

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • Source/ThirdParty/basis_transcoder.wasm • Source/ThirdParty/draco_decoder.wasm • Source/ThirdParty/wasm_splats_bg.wasm • Source/ThirdParty/zip-module.wasm

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.

v23.0.0

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • Source/ThirdParty/basis_transcoder.wasm • Source/ThirdParty/draco_decoder.wasm • Source/ThirdParty/wasm_splats_bg.wasm • Source/ThirdParty/zip-module.wasm

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.

v22.3.0

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • Source/ThirdParty/basis_transcoder.wasm • Source/ThirdParty/draco_decoder.wasm • Source/ThirdParty/wasm_splats_bg.wasm • Source/ThirdParty/zip-module.wasm

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.

v22.2.0

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • Source/ThirdParty/basis_transcoder.wasm • Source/ThirdParty/draco_decoder.wasm • Source/ThirdParty/wasm_splats_bg.wasm • Source/ThirdParty/zip-module.wasm

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.

v22.1.0

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • Source/ThirdParty/basis_transcoder.wasm • Source/ThirdParty/draco_decoder.wasm • Source/ThirdParty/wasm_splats_bg.wasm • Source/ThirdParty/zip-module.wasm

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.