@needle-tools/gltf-build-pipeline No license 20 versions

@needle-tools/gltf-build-pipeline

npm Repository Homepage

Pipeline and tools for optimizing gltf files using gltf-transform and compression settings within glTF extensions

20

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

herbstmarwi123

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:glob	AI (phantom-deps): glob is a declared dep used transitively/in config; stable false positive for this package.	ai	2026/05/02
phantom-deps	phantom-dep:ndarray	AI (phantom-deps): ndarray declared dep used via config/indirect; stable false positive.	ai	2026/05/02
phantom-deps	phantom-dep:ndarray-pixels	AI (phantom-deps): ndarray-pixels declared dep used via config/indirect; stable false positive.	ai	2026/05/02
phantom-deps	phantom-dep:ndarray-lanczos	AI (phantom-deps): ndarray-lanczos declared dep used via config/indirect; stable false positive.	ai	2026/05/02
bogus-package	bogus-package	AI (bogus-package): Technical glTF pipeline tool; link-heavy README is documentation, not a phishing farm.	ai	2026/05/02

Versions (showing 20 of 20)

Version	Deps	Published
2.14.1	19 / 3	2026-04-13
2.14.0	19 / 3	2026-01-30
2.13.1	19 / 3	2026-01-30
2.13.0	19 / 3	2025-10-20
2.12.1	18 / 3	2025-09-15
2.12.0	18 / 3	2025-09-15
2.11.4	18 / 3	2025-08-18
2.11.3	18 / 3	2025-08-11
2.11.2	18 / 3	2025-08-07
2.11.1	18 / 3	2025-08-06
2.11.0	18 / 3	2025-08-04
2.10.2	18 / 3	2025-07-17
2.10.1	18 / 3	2025-07-09
2.10.0	18 / 3	2025-07-09
2.9.5	18 / 3	2025-05-23
2.9.4	18 / 3	2025-05-23
2.9.3	18 / 3	2025-05-22
2.9.2	18 / 3	2025-05-22
2.9.1	18 / 3	2025-05-22
2.9.0	18 / 3	2025-05-22

v2.14.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.

v2.14.0

1 finding

LOW No provenance attestation provenance

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

v2.13.1

1 finding

LOW No provenance attestation provenance

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

v2.13.0

1 finding

LOW No provenance attestation provenance

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

v2.12.1

1 finding

LOW No provenance attestation provenance

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

v2.12.0

1 finding

LOW No provenance attestation provenance

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

v2.11.4

1 finding

LOW No provenance attestation provenance

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

v2.11.3

1 finding

LOW No provenance attestation provenance

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

v2.11.2

1 finding

LOW No provenance attestation provenance

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

v2.11.1

1 finding

LOW No provenance attestation provenance

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

v2.11.0

1 finding

LOW No provenance attestation provenance

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

v2.10.2

1 finding

LOW No provenance attestation provenance

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

v2.10.1

1 finding

LOW No provenance attestation provenance

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

v2.10.0

1 finding

LOW No provenance attestation provenance

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

v2.9.5

1 finding

LOW No provenance attestation provenance

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

v2.9.4

1 finding

LOW No provenance attestation provenance

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

v2.9.3

1 finding

LOW No provenance attestation provenance

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

v2.9.2

1 finding

LOW No provenance attestation provenance

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

v2.9.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.

v2.9.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.