whatwg-url-minimum
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): CI-based publish via changesets; gitHead omission is a known GitHub Actions artifact. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Changesets CLI publishes multiple versions in quick succession; expected for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal README and empty keywords are normal for a focused utility; 1.3M downloads confirm legitimacy. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.1.2 | 0 / 21 | |
| 0.1.1 | 0 / 21 | |
| 0.1.0 | 0 / 21 | |
| 0.0.1 | 0 / 21 |
v0.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.