parse5-htmlparser2-tree-adapter
htmlparser2 tree adapter for parse5.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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): rreverser is a known contributor to parse5; legitimate maintainer transition in 2018 with strong publisher track record. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2018, before Sigstore provenance existed. Expected for this era of packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 8.0.1 | 2 / 0 | |
| 8.0.0 | 2 / 0 | |
| 7.1.0 | 2 / 0 | |
| 7.0.0 | 2 / 0 | |
| 6.0.1 | 1 / 0 | |
| 6.0.0 | 1 / 0 | |
| 5.1.1 | 1 / 0 | |
| 5.1.0 | 1 / 0 | |
| 5.0.0 | 1 / 0 |
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-10-12. This could indicate a legitimate maintainer transition or an account compromise.
v7.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-20. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.0
2 findingsThis version was published by a different npm account than previous versions on 2018-08-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.