html-parse-stringify
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Diff vs prior approved version shows no new large files or dep/script changes; consistent with build output growth. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Established trusted publisher with long track record; no takeover behavior evident. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transfer to established publisher adrai; no code changes. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 0 / 7 | |
| 4.0.0 | 0 / 7 | |
| 3.1.0 | 1 / 5 | |
| 3.0.1 | 1 / 5 | |
| 3.0.0 | 1 / 5 |
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-22. 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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.