@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 34 of 134)
| Version | Deps | Published |
|---|---|---|
| 6.15.5 | 25 / 20 | |
| 6.15.4 | 25 / 20 | |
| 6.15.3 | 25 / 20 | |
| 6.15.2 | 25 / 20 | |
| 6.15.1 | 25 / 20 | |
| 6.15.0 | 25 / 20 | |
| 6.14.13 | 25 / 20 | |
| 6.14.12 | 25 / 20 | |
| 6.14.11 | 25 / 20 | |
| 6.14.10 | 25 / 20 | |
| 6.14.9 | 25 / 20 | |
| 6.14.8 | 25 / 20 | |
| 6.14.7 | 25 / 20 | |
| 6.14.6 | 25 / 20 | |
| 6.14.5 | 25 / 20 | |
| 6.14.4 | 25 / 20 | |
| 6.14.3 | 25 / 20 | |
| 6.14.2 | 25 / 20 | |
| 6.14.1 | 25 / 20 | |
| 6.14.0 | 25 / 20 | |
| 6.13.0 | 25 / 20 | |
| 6.12.10 | 25 / 20 | |
| 6.12.9 | 25 / 20 | |
| 6.12.8 | 25 / 20 | |
| 6.12.7 | 25 / 20 | |
| 6.12.6 | 25 / 20 | |
| 6.12.5 | 25 / 20 | |
| 6.12.4 | 25 / 20 | |
| 6.12.3 | 25 / 20 | |
| 6.12.2 | 25 / 20 | |
| 6.12.1 | 25 / 20 | |
| 6.12.0 | 25 / 20 | |
| 6.11.0 | 25 / 20 | |
| 6.10.3 | 27 / 20 |
v6.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.