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 100 of 409)
| Version | Deps | Published |
|---|---|---|
| 1.23.26 | 0 / 19 | |
| 1.23.25 | 0 / 19 | |
| 1.23.24 | 0 / 19 | |
| 1.23.23 | 0 / 19 | |
| 1.23.22 | 0 / 19 | |
| 1.23.21 | 0 / 19 | |
| 1.23.20 | 0 / 19 | |
| 1.23.19 | 0 / 19 | |
| 1.23.18 | 0 / 19 | |
| 1.23.17 | 0 / 19 | |
| 1.23.16 | 0 / 19 | |
| 1.23.15 | 0 / 19 | |
| 1.23.14 | 0 / 19 | |
| 1.23.13 | 0 / 19 | |
| 1.23.12 | 0 / 19 | |
| 1.23.11 | 0 / 19 | |
| 1.23.10 | 0 / 19 | |
| 1.23.9 | 0 / 19 | |
| 1.23.8 | 0 / 19 | |
| 1.23.7 | 0 / 19 | |
| 1.23.6 | 0 / 19 | |
| 1.23.5 | 0 / 19 | |
| 1.23.4 | 0 / 19 | |
| 1.23.3 | 0 / 19 | |
| 1.23.2 | 0 / 19 | |
| 1.23.1 | 0 / 19 | |
| 1.23.0 | 0 / 19 | |
| 1.22.55 | 0 / 19 | |
| 1.22.54 | 0 / 19 | |
| 1.22.53 | 0 / 19 | |
| 1.22.52 | 0 / 19 | |
| 1.22.51 | 0 / 19 | |
| 1.22.50 | 0 / 19 | |
| 1.22.49 | 0 / 19 | |
| 1.22.48 | 0 / 19 | |
| 1.22.47 | 0 / 19 | |
| 1.22.46 | 0 / 19 | |
| 1.22.45 | 0 / 19 | |
| 1.22.44 | 0 / 19 | |
| 1.22.43 | 0 / 19 | |
| 1.22.42 | 0 / 19 | |
| 1.22.41 | 0 / 19 | |
| 1.22.40 | 0 / 19 | |
| 1.22.39 | 0 / 19 | |
| 1.22.38 | 0 / 19 | |
| 1.22.37 | 0 / 19 | |
| 1.22.36 | 0 / 19 | |
| 1.22.35 | 0 / 19 | |
| 1.22.34 | 0 / 19 | |
| 1.22.33 | 0 / 19 | |
| 1.22.32 | 0 / 19 | |
| 1.22.31 | 0 / 19 | |
| 1.22.30 | 0 / 19 | |
| 1.22.29 | 0 / 19 | |
| 1.22.28 | 0 / 19 | |
| 1.22.27 | 0 / 19 | |
| 1.22.26 | 0 / 19 | |
| 1.22.25 | 0 / 19 | |
| 1.22.24 | 0 / 19 | |
| 1.22.23 | 0 / 19 | |
| 1.22.22 | 0 / 19 | |
| 1.22.21 | 0 / 19 | |
| 1.22.20 | 0 / 19 | |
| 1.22.19 | 0 / 19 | |
| 1.22.18 | 0 / 19 | |
| 1.22.17 | 0 / 19 | |
| 1.22.16 | 0 / 19 | |
| 1.22.15 | 0 / 19 | |
| 1.22.14 | 0 / 19 | |
| 1.22.13 | 0 / 19 | |
| 1.22.12 | 0 / 19 | |
| 1.22.11 | 0 / 19 | |
| 1.22.10 | 0 / 19 | |
| 1.22.9 | 0 / 19 | |
| 1.22.8 | 0 / 19 | |
| 1.22.7 | 0 / 19 | |
| 1.22.6 | 0 / 19 | |
| 1.22.5 | 0 / 19 | |
| 1.22.4 | 0 / 19 | |
| 1.22.3 | 0 / 19 | |
| 1.22.2 | 0 / 19 | |
| 1.22.1 | 0 / 19 | |
| 1.22.0 | 0 / 19 | |
| 1.21.101 | 0 / 19 | |
| 1.21.100 | 0 / 19 | |
| 1.21.99 | 0 / 19 | |
| 1.21.98 | 0 / 19 | |
| 1.21.97 | 0 / 19 | |
| 1.21.96 | 0 / 19 | |
| 1.21.95 | 0 / 19 | |
| 1.21.94 | 0 / 19 | |
| 1.21.93 | 0 / 19 | |
| 1.21.92 | 0 / 19 | |
| 1.21.91 | 0 / 19 | |
| 1.21.90 | 0 / 19 | |
| 1.21.89 | 0 / 19 | |
| 1.21.88 | 0 / 19 | |
| 1.21.87 | 0 / 19 | |
| 1.21.86 | 0 / 19 | |
| 1.21.85 | 0 / 19 |
v1.23.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.