stream-markdown-parser
Pure markdown parser and renderer utilities with streaming support - framework agnostic
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-established, widely-used library; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with clean track record; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:markdown-it-sup | AI (phantom-deps): Same dynamic plugin loading pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:markdown-it-mark | AI (phantom-deps): Same dynamic plugin loading pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:markdown-it-ins | AI (phantom-deps): markdown-it plugins loaded via config/dynamic registration, not direct imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:markdown-it-container | AI (phantom-deps): Same dynamic plugin loading pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:markdown-it-task-checkbox | AI (phantom-deps): Same dynamic plugin loading pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:markdown-it-footnote | AI (phantom-deps): Same dynamic plugin loading pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:markdown-it-sub | AI (phantom-deps): Same dynamic plugin loading pattern; stable false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 8 / 4 | |
| 1.0.2 | 8 / 4 | |
| 1.0.1 | 8 / 4 | |
| 1.0.0 | 8 / 4 | |
| 0.0.90 | 8 / 4 | |
| 0.0.89 | 8 / 4 | |
| 0.0.88 | 8 / 4 | |
| 0.0.87 | 8 / 4 | |
| 0.0.85 | 8 / 4 | |
| 0.0.81 | 8 / 4 | |
| 0.0.80 | 8 / 4 | |
| 0.0.28 | 9 / 4 | |
| 0.0.12 | 9 / 5 | |
| 0.0.2 | 9 / 5 | |
| 0.0.1 | 0 / 9 |
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.