rehype-stringify
rehype plugin to serialize HTML
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): unified and @types/hast are core ecosystem packages for rehype plugins; their addition is expected and benign for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Mass-production signal is false positive for prolific legitimate maintainer; empty-main is standard TypeScript entry point pattern with implementation in lib/. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): remcohaszing is a known contributor to the unified/rehype ecosystem; this is a legitimate maintainer addition to a well-established open-source project. | ai | |
| phantom-deps | phantom-dep:@types/hast | AI (phantom-deps): @types/hast is a TypeScript type package used for type checking in the unified ecosystem; not being directly imported at runtime is expected and benign. | ai | |
| dependencies | unvetted-dep:@types/hast | AI (dependencies): @types/hast is a standard TypeScript type definition package in the unified/hast ecosystem; its use here is legitimate and expected. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 10.0.1 | 3 / 0 | |
| 10.0.0 | 3 / 0 | |
| 9.0.4 | 3 / 0 | |
| 9.0.3 | 3 / 0 | |
| 9.0.2 | 3 / 0 | |
| 9.0.1 | 3 / 0 | |
| 9.0.0 | 3 / 0 | |
| 8.0.0 | 1 / 0 | |
| 7.0.0 | 2 / 0 | |
| 6.0.1 | 2 / 0 | |
| 6.0.0 | 2 / 0 | |
| 5.0.0 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.0.0 | 2 / 0 | |
| 2.1.0 | 2 / 0 | |
| 2.0.0 | 2 / 0 | |
| 1.0.0 | 3 / 0 | |
| 0.0.0 | 3 / 0 |
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.