← Home

markdown-to-ast

Parse Markdown to AST with location info.

26
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

azu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established package from trusted publisher azu with 253 approved packages; lack of Sigstore provenance is a process gap, not a security risk for this package. ai

Versions (showing 26 of 26)

Version Deps Published
6.0.3 5 / 13
6.0.2 5 / 12
6.0.1 5 / 12
6.0.0 5 / 12
5.0.0 5 / 12
4.0.0 5 / 12
3.4.0 4 / 8
3.2.3 4 / 7
3.2.1 4 / 6
3.2.0 4 / 7
3.1.1 4 / 6
3.0.7 4 / 6
3.0.5 4 / 6
3.0.3 3 / 7
3.0.2 3 / 7
3.0.1 3 / 7
3.0.0 3 / 7
2.2.1 6 / 7
2.2.0 5 / 7
2.1.0 5 / 7
2.0.0 5 / 7
1.2.0 5 / 7
1.1.1 5 / 7
1.1.0 5 / 7
1.0.2 5 / 7
1.0.1 5 / 7

v6.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.2

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: azu.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.1

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: azu.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: azu.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: azu.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.