draco3d — Greenflagged

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

zhafangfrankgalliganondystomfineganvytyaz

Keywords

geometrycompressionmeshpoint cloud

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:draco_decoder_nodejs.js	AI (source-diff): Emscripten/WASM build output for the decoder; benign and stable for this package.	ai	2026/07/21
source-diff	encoded-string-file:draco_encoder_nodejs.js	AI (source-diff): Emscripten/WASM build output for the encoder; benign and stable for this package.	ai	2026/07/21
npm-metadata	bundled-binaries	AI (npm-metadata): WASM decoder/encoder are the package's core function; stable across versions.	ai	2026/07/21
maintainer-change	maintainer-added	AI (maintainer-change): Long-stable Google Draco team maintainer set; benign.	ai	2026/07/21

Versions (showing 27 of 27)

Version	Deps	Published
1.5.7	0 / 0	2024-01-17
1.5.6	0 / 0	2023-02-07
1.5.5	0 / 0	2022-10-29
1.5.4	0 / 0	2022-10-27
1.5.3	0 / 0	2022-07-07
1.5.2	0 / 0	2022-02-17
1.5.1	0 / 0	2022-02-15
1.5.0	0 / 0	2021-12-08
1.4.3	0 / 0	2021-10-11
1.4.1	0 / 0	2020-12-08
1.4.0	0 / 0	2020-12-01
1.3.6	0 / 0	2020-03-03
1.3.4	0 / 0	2018-08-23
1.3.3	0 / 0	2018-06-15
1.3.2	0 / 0	2018-06-05
1.3.1	0 / 0	2018-05-02
1.3.0	0 / 0	2018-04-18
1.2.6	0 / 0	2018-04-05
1.2.5	0 / 0	2018-01-16
1.2.4	0 / 0	2017-12-13
1.2.2	0 / 0	2017-11-10
1.2.1	0 / 0	2017-11-10
1.2.0	0 / 0	2017-11-10
1.1.0	0 / 0	2017-09-11
1.0.3	0 / 0	2017-08-21
1.0.2	0 / 0	2017-07-28
1.0.0	0 / 0	2017-07-21

v1.5.6

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • draco_decoder.wasm • draco_encoder.wasm

LOW No provenance attestation provenance

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

INFO Publisher changed: frankgalligan → ondys (on 2023-02-07, known maintainer) provenance

This version was published by a different npm account (ondys) than the most recent previously approved version (frankgalligan) on 2023-02-07, but ondys 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.

v1.5.5

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • draco_decoder.wasm • draco_encoder.wasm

MEDIUM Publisher changed: frankgalligan → tomfinegan (on 2022-10-29, unremoved on npm for 1361d) provenance

This version was published by a different npm account (tomfinegan) than the most recent previously approved version (frankgalligan) on 2022-10-29. It has since remained available on npm for 1361 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.4

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • draco_decoder.wasm • draco_encoder.wasm

MEDIUM Publisher changed: frankgalligan → tomfinegan (on 2022-10-27, unremoved on npm for 1362d) provenance

This version was published by a different npm account (tomfinegan) than the most recent previously approved version (frankgalligan) on 2022-10-27. It has since remained available on npm for 1362 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.3

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • draco_decoder.wasm • draco_encoder.wasm

MEDIUM Publisher changed: frankgalligan → tomfinegan (on 2022-07-07, unremoved on npm for 1474d) provenance

This version was published by a different npm account (tomfinegan) than the most recent previously approved version (frankgalligan) on 2022-07-07. It has since remained available on npm for 1474 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.2

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • draco_decoder.wasm • draco_encoder.wasm

MEDIUM Publisher changed: frankgalligan → tomfinegan (on 2022-02-17, unremoved on npm for 1614d) provenance

This version was published by a different npm account (tomfinegan) than the most recent previously approved version (frankgalligan) on 2022-02-17. It has since remained available on npm for 1614 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.1

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • draco_decoder.wasm • draco_encoder.wasm

MEDIUM Publisher changed: frankgalligan → tomfinegan (on 2022-02-15, unremoved on npm for 1616d) provenance

This version was published by a different npm account (tomfinegan) than the most recent previously approved version (frankgalligan) on 2022-02-15. It has since remained available on npm for 1616 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.0

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • draco_decoder.wasm • draco_encoder.wasm

MEDIUM Publisher changed: frankgalligan → tomfinegan (on 2021-12-08, unremoved on npm for 1685d) provenance

This version was published by a different npm account (tomfinegan) than the most recent previously approved version (frankgalligan) on 2021-12-08. It has since remained available on npm for 1685 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.3

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • draco_decoder.wasm • draco_encoder.wasm

MEDIUM Publisher changed: frankgalligan → tomfinegan (on 2021-10-11, unremoved on npm for 1743d) provenance

This version was published by a different npm account (tomfinegan) than the most recent previously approved version (frankgalligan) on 2021-10-11. It has since remained available on npm for 1743 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.1

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • draco_decoder.wasm • draco_encoder.wasm

MEDIUM Publisher changed: frankgalligan → tomfinegan (on 2020-12-08, unremoved on npm for 2051d) provenance

This version was published by a different npm account (tomfinegan) than the most recent previously approved version (frankgalligan) on 2020-12-08. It has since remained available on npm for 2051 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.0

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • draco_decoder.wasm • draco_encoder.wasm

MEDIUM Publisher changed: frankgalligan → tomfinegan (on 2020-12-01, unremoved on npm for 2057d) provenance

This version was published by a different npm account (tomfinegan) than the most recent previously approved version (frankgalligan) on 2020-12-01. It has since remained available on npm for 2057 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.3.6

3 findings

HIGH Long encoded string in modified file: draco_decoder_nodejs.js source-diff

Modified file contains 8 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: draco_encoder_nodejs.js source-diff

Modified file contains 8 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.3.4

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.6

1 finding

LOW No provenance attestation provenance

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

v1.2.5

2 findings

MEDIUM Publisher changed: zhafang → frankgalligan (on 2018-01-16, unremoved on npm for 3107d) provenance

This version was published by a different npm account (frankgalligan) than the most recent previously approved version (zhafang) on 2018-01-16. It has since remained available on npm for 3107 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

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

v1.2.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.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

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