global-tld-list
List of Global TLDs
Supply chain provenance
Status for the latest visible version.
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): Publisher changed to GitHub Actions with valid SLSA Sigstore attestation from the original repo (mastermunj/global-tld-list). This is a legitimate CI/CD migration, stable for this package going forward. | ai |
Versions (showing 8 of 409)
| Version | Deps | Published |
|---|---|---|
| 1.20.1 | 0 / 21 | |
| 1.20.0 | 0 / 21 | |
| 1.19.5 | 0 / 21 | |
| 1.19.4 | 0 / 21 | |
| 1.19.3 | 0 / 21 | |
| 1.19.2 | 0 / 21 | |
| 1.19.1 | 0 / 21 | |
| 1.19.0 | 0 / 21 |
v1.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.