tldts-experimental
Library to work against complex domain names, subdomains and URIs.
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): Package now publishes via GitHub Actions with SLSA attestation; this is a legitimate CI/CD transition for this repo. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 7.4.9 | 1 / 14 | |
| 7.4.8 | 1 / 14 | |
| 7.4.7 | 1 / 14 | |
| 7.4.6 | 1 / 14 | |
| 7.4.5 | 1 / 14 | |
| 7.4.4 | 1 / 14 | |
| 7.4.3 | 1 / 14 | |
| 7.4.2 | 1 / 14 | |
| 7.4.1 | 1 / 14 | |
| 7.4.0 | 1 / 14 | |
| 7.3.1 | 1 / 14 | |
| 7.3.0 | 1 / 14 | |
| 7.2.1 | 1 / 14 | |
| 7.2.0 | 1 / 14 | |
| 7.1.2 | 1 / 14 | |
| 7.1.1 | 1 / 14 | |
| 7.1.0 | 1 / 14 | |
| 7.0.32 | 1 / 14 | |
| 7.0.31 | 1 / 14 | |
| 7.0.30 | 1 / 14 | |
| 7.0.29 | 1 / 14 | |
| 7.0.28 | 1 / 14 | |
| 7.0.27 | 1 / 14 | |
| 7.0.26 | 1 / 14 | |
| 7.0.25 | 1 / 14 | |
| 7.0.24 | 1 / 14 | |
| 7.0.23 | 1 / 14 | |
| 7.0.22 | 1 / 14 | |
| 7.0.21 | 1 / 14 | |
| 7.0.20 | 1 / 14 | |
| 7.0.19 | 1 / 14 | |
| 7.0.18 | 1 / 14 | |
| 7.0.17 | 1 / 14 | |
| 7.0.16 | 1 / 14 | |
| 7.0.15 | 1 / 14 | |
| 7.0.14 | 1 / 14 | |
| 7.0.13 | 1 / 14 | |
| 7.0.12 | 1 / 14 | |
| 7.0.11 | 1 / 14 | |
| 7.0.10 | 1 / 14 | |
| 7.0.9 | 1 / 14 | |
| 7.0.8 | 1 / 14 | |
| 7.0.7 | 1 / 14 | |
| 7.0.6 | 1 / 14 | |
| 7.0.5 | 1 / 14 | |
| 7.0.4 | 1 / 14 | |
| 7.0.3 | 1 / 14 | |
| 7.0.2 | 1 / 14 | |
| 7.0.1 | 1 / 14 | |
| 7.0.0 | 1 / 14 |
v7.4.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.