@gjsify/example-dom-webgl-tutorial-04
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Intentionally minimal example package; missing description is not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@gjsify/webgl | AI (phantom-deps): Same-org dependency used as a runtime dep in a tutorial example; phantom-dep heuristic is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Example/tutorial package from established @gjsify org; sparse metadata is expected for org-internal examples. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.7 | 1 / 9 | |
| 0.1.6 | 1 / 9 | |
| 0.1.5 | 1 / 9 | |
| 0.1.4 | 1 / 9 | |
| 0.1.3 | 1 / 9 |
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.