@loaders.gl/3d-tiles
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/dist.dev.js | AI (source-diff): Embedded WASM decoder base string in bundled dist output; stable build artifact for this package. | ai | |
| source-diff | encoded-string-file:dist/dist.min.js | AI (source-diff): dist/dist.min.js is a webpack UMD bundle built by the package's own build script; long encoded strings are normal minification artifacts. | ai | |
| provenance | no-provenance | AI (provenance): Established visgl monorepo package; lack of provenance is consistent across all versions. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 4.4.3 | 14 / 0 | |
| 4.4.2 | 14 / 0 | |
| 4.4.1 | 14 / 0 | |
| 4.4.0 | 14 / 0 | |
| 4.3.4 | 14 / 0 | |
| 4.3.3 | 14 / 0 | |
| 4.3.2 | 14 / 0 | |
| 4.3.1 | 14 / 0 | |
| 4.3.0 | 14 / 0 | |
| 4.2.5 | 14 / 0 | |
| 4.2.4 | 14 / 0 | |
| 4.2.3 | 14 / 0 | |
| 4.2.2 | 14 / 0 |
v4.3.3
2 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
2 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
2 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
2 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (belom88) than the most recent previously approved version (dterekhova) on 2024-09-20, but belom88 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.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.