@gjsify/dom-exception
DOMException polyfill for GJS (WebIDL standard)
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from jumplink to GitHub Actions CI is consistent with automation migration; no code changes accompany the publisher shift. | ai | |
| provenance | missing-githead | AI (provenance): Established gjsify package with clean history; missing gitHead is a CI environment change, not a malware indicator. | ai |
Versions (showing 51 of 114)
| Version | Deps | Published |
|---|---|---|
| 0.22.0 | 0 / 4 | |
| 0.21.0 | 0 / 4 | |
| 0.20.0 | 0 / 4 | |
| 0.19.0 | 0 / 4 | |
| 0.18.0 | 0 / 4 | |
| 0.17.0 | 0 / 4 | |
| 0.16.9 | 0 / 4 | |
| 0.16.8 | 0 / 4 | |
| 0.16.7 | 0 / 4 | |
| 0.16.6 | 0 / 4 | |
| 0.16.5 | 0 / 4 | |
| 0.16.4 | 0 / 4 | |
| 0.16.3 | 0 / 4 | |
| 0.16.2 | 0 / 4 | |
| 0.16.1 | 0 / 4 | |
| 0.16.0 | 0 / 4 | |
| 0.15.1 | 0 / 4 | |
| 0.14.0 | 0 / 4 | |
| 0.13.2 | 0 / 4 | |
| 0.13.1 | 0 / 4 | |
| 0.13.0 | 0 / 4 | |
| 0.12.0 | 0 / 4 | |
| 0.11.0 | 0 / 4 | |
| 0.10.0 | 0 / 4 | |
| 0.9.0 | 0 / 4 | |
| 0.8.0 | 0 / 4 | |
| 0.7.5 | 0 / 4 | |
| 0.7.4 | 0 / 4 | |
| 0.7.3 | 0 / 4 | |
| 0.7.2 | 0 / 4 | |
| 0.7.0 | 0 / 4 | |
| 0.6.1 | 0 / 4 | |
| 0.6.0 | 0 / 4 | |
| 0.5.2 | 0 / 4 | |
| 0.5.1 | 0 / 4 | |
| 0.5.0 | 0 / 4 | |
| 0.4.44 | 0 / 4 | |
| 0.4.43 | 0 / 4 | |
| 0.4.42 | 0 / 4 | |
| 0.4.41 | 0 / 4 | |
| 0.4.40 | 0 / 4 | |
| 0.4.39 | 0 / 4 | |
| 0.4.38 | 0 / 4 | |
| 0.4.37 | 0 / 4 | |
| 0.4.36 | 0 / 4 | |
| 0.4.35 | 0 / 4 | |
| 0.4.34 | 0 / 4 | |
| 0.4.33 | 0 / 4 | |
| 0.4.32 | 0 / 4 | |
| 0.4.31 | 0 / 4 | |
| 0.4.30 | 0 / 4 |
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.