@adobe/helix-html-pipeline
Helix HTML Pipeline
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): Adobe package publishing via GitHub Actions with SLSA attestation; legitimate CI/CD migration, stable for this package. | ai | |
| dependencies | unvetted-dep:mdast-util-to-string | AI (dependencies): mdast-util-to-string is a well-known unified ecosystem package; stable false positive for this package. | ai |
Versions (showing 100 of 134)
| Version | Deps | Published |
|---|---|---|
| 6.29.9 | 26 / 21 | |
| 6.29.8 | 26 / 21 | |
| 6.29.6 | 26 / 21 | |
| 6.29.5 | 26 / 21 | |
| 6.29.4 | 26 / 21 | |
| 6.29.3 | 26 / 21 | |
| 6.29.2 | 26 / 21 | |
| 6.29.1 | 26 / 21 | |
| 6.28.6 | 26 / 21 | |
| 6.28.3 | 26 / 21 | |
| 6.28.2 | 26 / 21 | |
| 6.28.1 | 26 / 21 | |
| 6.28.0 | 26 / 21 | |
| 6.27.30 | 26 / 21 | |
| 6.27.29 | 26 / 21 | |
| 6.27.28 | 26 / 21 | |
| 6.27.27 | 26 / 21 | |
| 6.27.26 | 26 / 21 | |
| 6.27.25 | 26 / 21 | |
| 6.27.24 | 26 / 21 | |
| 6.27.23 | 26 / 21 | |
| 6.27.22 | 26 / 21 | |
| 6.27.21 | 26 / 21 | |
| 6.27.20 | 26 / 21 | |
| 6.27.19 | 26 / 21 | |
| 6.27.18 | 26 / 21 | |
| 6.27.17 | 26 / 21 | |
| 6.27.16 | 26 / 21 | |
| 6.27.15 | 26 / 21 | |
| 6.27.14 | 26 / 21 | |
| 6.27.13 | 26 / 21 | |
| 6.27.12 | 26 / 21 | |
| 6.27.11 | 26 / 21 | |
| 6.27.10 | 26 / 21 | |
| 6.27.9 | 26 / 21 | |
| 6.27.8 | 26 / 21 | |
| 6.27.7 | 26 / 21 | |
| 6.27.6 | 26 / 21 | |
| 6.27.5 | 26 / 21 | |
| 6.27.4 | 26 / 21 | |
| 6.27.3 | 26 / 21 | |
| 6.27.2 | 26 / 21 | |
| 6.27.1 | 26 / 21 | |
| 6.27.0 | 26 / 21 | |
| 6.26.8 | 26 / 21 | |
| 6.26.7 | 26 / 21 | |
| 6.26.6 | 26 / 21 | |
| 6.26.5 | 26 / 21 | |
| 6.26.4 | 26 / 21 | |
| 6.26.3 | 26 / 21 | |
| 6.26.2 | 26 / 21 | |
| 6.26.1 | 26 / 21 | |
| 6.26.0 | 26 / 21 | |
| 6.25.5 | 26 / 21 | |
| 6.25.4 | 26 / 21 | |
| 6.25.3 | 26 / 20 | |
| 6.25.2 | 26 / 20 | |
| 6.25.1 | 26 / 20 | |
| 6.25.0 | 26 / 20 | |
| 6.24.3 | 26 / 20 | |
| 6.24.2 | 26 / 20 | |
| 6.24.1 | 26 / 20 | |
| 6.24.0 | 26 / 20 | |
| 6.23.0 | 26 / 20 | |
| 6.22.0 | 26 / 20 | |
| 6.21.6 | 26 / 20 | |
| 6.21.5 | 26 / 20 | |
| 6.21.4 | 26 / 20 | |
| 6.21.3 | 27 / 20 | |
| 6.21.2 | 27 / 20 | |
| 6.21.1 | 27 / 20 | |
| 6.21.0 | 27 / 20 | |
| 6.20.4 | 27 / 20 | |
| 6.20.3 | 27 / 20 | |
| 6.20.2 | 27 / 20 | |
| 6.20.1 | 27 / 20 | |
| 6.20.0 | 27 / 20 | |
| 6.19.1 | 26 / 20 | |
| 6.19.0 | 27 / 20 | |
| 6.18.4 | 26 / 20 | |
| 6.18.3 | 26 / 20 | |
| 6.18.2 | 26 / 20 | |
| 6.18.1 | 26 / 20 | |
| 6.18.0 | 26 / 20 | |
| 6.17.8 | 26 / 20 | |
| 6.17.7 | 26 / 20 | |
| 6.17.6 | 26 / 20 | |
| 6.17.5 | 26 / 20 | |
| 6.17.4 | 26 / 20 | |
| 6.17.3 | 26 / 20 | |
| 6.17.2 | 26 / 20 | |
| 6.17.1 | 26 / 20 | |
| 6.17.0 | 26 / 20 | |
| 6.16.0 | 26 / 20 | |
| 6.15.11 | 25 / 20 | |
| 6.15.10 | 25 / 20 | |
| 6.15.9 | 25 / 20 | |
| 6.15.8 | 25 / 20 | |
| 6.15.7 | 25 / 20 | |
| 6.15.6 | 25 / 20 |
v6.29.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.29.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.24.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.