@gjsify/web-polyfills
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@gjsify/message-channel | AI (phantom-deps): Meta package; all deps are re-exported transitively, not directly imported. | ai | |
| phantom-deps | phantom-dep:@gjsify/gamepad | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/formdata | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/webaudio | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/domparser | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/webcrypto | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/websocket | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/dom-events | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/webstorage | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/fetch | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/web-globals | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/web-streams | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/webassembly | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/dom-exception | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/xmlhttprequest | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/abort-controller | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/compression-streams | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai | |
| phantom-deps | phantom-dep:@gjsify/eventsource | AI (phantom-deps): Meta package with no direct imports; all deps are same-org siblings re-exported by design. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.4.21 | 18 / 0 | |
| 0.4.5 | 17 / 0 | |
| 0.4.4 | 17 / 0 | |
| 0.4.3 | 17 / 0 | |
| 0.4.0 | 17 / 0 | |
| 0.3.21 | 17 / 0 | |
| 0.3.20 | 17 / 0 | |
| 0.3.19 | 17 / 0 | |
| 0.1.7 | 11 / 0 | |
| 0.1.6 | 11 / 0 | |
| 0.1.5 | 11 / 0 | |
| 0.1.4 | 11 / 0 | |
| 0.1.3 | 11 / 0 | |
| 0.1.2 | 11 / 0 |
v0.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.