@thi.ng/webgl
WebGL & GLSL abstraction layer
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@thi.ng/memoize | AI (dependencies): Internal thi.ng monorepo sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/vectors | AI (dependencies): Internal thi.ng monorepo sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/matrices | AI (dependencies): Internal thi.ng monorepo sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/shader-ast | AI (dependencies): Internal thi.ng monorepo sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/transducers | AI (dependencies): Internal thi.ng monorepo sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/object-utils | AI (dependencies): Internal thi.ng monorepo sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/vector-pools | AI (dependencies): Internal thi.ng monorepo sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/shader-ast-glsl | AI (dependencies): Internal thi.ng monorepo sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/shader-ast-stdlib | AI (dependencies): Internal thi.ng monorepo sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Internal thi.ng monorepo sibling dep; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@thi.ng/pixel | AI (dependencies): Internal thi.ng monorepo sibling dep. | ai | |
| provenance | no-provenance | AI (provenance): Established thi.ng/umbrella monorepo; no provenance is consistent across all its packages. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 6.9.114 | 16 / 3 | |
| 6.9.113 | 16 / 3 | |
| 6.9.112 | 16 / 3 | |
| 6.9.110 | 16 / 3 | |
| 6.9.109 | 16 / 3 | |
| 6.9.107 | 16 / 3 | |
| 6.9.106 | 16 / 3 | |
| 6.9.105 | 16 / 3 | |
| 6.9.104 | 16 / 3 | |
| 6.9.103 | 16 / 3 | |
| 6.9.102 | 16 / 3 | |
| 6.9.101 | 16 / 3 | |
| 6.9.100 | 16 / 3 | |
| 6.9.99 | 16 / 3 | |
| 6.9.98 | 16 / 3 | |
| 6.9.97 | 16 / 3 | |
| 6.9.95 | 16 / 3 | |
| 6.9.94 | 16 / 3 | |
| 6.9.93 | 16 / 3 | |
| 6.9.92 | 16 / 3 | |
| 6.9.91 | 16 / 3 | |
| 6.9.90 | 16 / 3 | |
| 6.9.89 | 16 / 3 | |
| 6.9.87 | 16 / 3 | |
| 6.9.86 | 16 / 3 | |
| 6.9.85 | 16 / 3 | |
| 6.9.84 | 16 / 3 | |
| 6.9.83 | 16 / 3 | |
| 6.9.79 | 16 / 3 | |
| 6.9.78 | 16 / 3 | |
| 6.9.77 | 16 / 3 | |
| 6.9.76 | 16 / 3 | |
| 6.9.75 | 16 / 3 | |
| 6.9.74 | 16 / 3 | |
| 6.9.73 | 16 / 3 | |
| 6.9.72 | 16 / 3 | |
| 6.9.71 | 16 / 3 | |
| 6.9.70 | 16 / 3 | |
| 6.9.69 | 16 / 3 | |
| 6.9.68 | 16 / 3 | |
| 6.9.67 | 16 / 3 | |
| 6.9.65 | 16 / 3 | |
| 6.9.64 | 16 / 3 | |
| 6.9.63 | 16 / 3 | |
| 6.9.62 | 16 / 3 | |
| 6.9.61 | 16 / 3 | |
| 6.9.60 | 16 / 3 | |
| 6.9.59 | 16 / 3 | |
| 6.9.58 | 16 / 3 | |
| 6.9.57 | 16 / 3 | |
| 6.9.56 | 16 / 3 |
v6.9.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.