@davidsneighbour/htmlvalidate-config
HTML Validate configuration for use in @davidsneighbour projects.
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 | publisher-changed | AI (provenance): Publisher is GitHub Actions CI/CD with SLSA attestation; this is the documented publish mechanism for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD migration; SLSA attestation confirms legitimate publish pipeline. | ai | |
| phantom-deps | phantom-dep:axe-core | AI (phantom-deps): Config package; deps referenced in config files rather than directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:html-validate | AI (phantom-deps): Config package; deps referenced in config files rather than directly imported — expected pattern. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2026.0.6 | 2 / 0 | |
| 2026.0.5 | 2 / 0 | |
| 2026.0.4 | 2 / 0 | |
| 2026.0.3 | 2 / 0 | |
| 2026.0.2 | 2 / 0 | |
| 2026.0.1 | 2 / 0 | |
| 2025.3.7 | 2 / 0 | |
| 2025.3.6 | 2 / 0 |
v2026.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-04-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2025.3.7
2 findingsThis version was published by a different npm account than previous versions on 2026-01-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2025.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.