← Home

myst-parser

npm Repository Homepage

Markdown parser for MyST markdown in JavaScript

7
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

rowanc1stevejpurvesebp-bot

Keywords

markdown-it-pluginmarkdown-itmarkdownmystjupyterjupyter-book

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from ebp-bot to GitHub Actions CI is consistent with jupyter-book/mystmd org automation; SLSA attestation confirms integrity. ai
publish-pattern dormant-publish AI (publish-pattern): SLSA provenance attestation confirms legitimate CI publish; dormancy explained by project migration to automated releases. ai
dependencies unvetted-dep:markdown-it AI (dependencies): markdown-it is a well-established, widely-used Markdown parser; not a novel or suspicious dependency for this package. ai
publish-pattern new-deps-added AI (publish-pattern): @types/markdown-it is a TS types package for existing dep markdown-it; not a meaningful attack surface. ai
provenance no-provenance AI (provenance): Established jupyter-book org package; lack of Sigstore attestation is a process gap, not a security risk here. ai
phantom-deps phantom-dep:@types/markdown-it AI (phantom-deps): @types/markdown-it is a TypeScript type package declared as a runtime dep for type exports; not a real phantom dep concern. ai

Versions (showing 7 of 7)

Version Deps Published
1.7.3 21 / 9
1.7.2 21 / 9
1.7.0 21 / 9
1.6.3 21 / 9
1.6.2 21 / 9
1.5.15 20 / 10
1.5.14 20 / 10

v1.7.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.7.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.7.0

2 findings
HIGH Publisher changed: ebp-bot → GitHub Actions (on 2026-03-03) provenance

This version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.3

1 finding
LOW No provenance attestation provenance

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

v1.6.2

1 finding
LOW No provenance attestation provenance

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

v1.5.15

1 finding
LOW No provenance attestation provenance

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

v1.5.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.