← Home

@podlite/markdown

npm Repository Homepage

Bidirectional Markdown support for Podlite — parse .md files, embed Markdown blocks

18
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

zaggaz

Keywords

podlitemarkdownmarkdown-parserparsermarkup-languageconverterbidirectionalmarkdown-to-astmarkupcompatibility

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:new-function-constructor AI (semgrep): Fires inside bundled AJV schema validator; standard pattern, not attacker-controlled. ai
phantom-deps phantom-dep:react AI (phantom-deps): react is a declared dependency; phantom-dep heuristic fails on bundled output. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): react-dom is a declared dependency; phantom-dep heuristic fails on bundled output. ai
phantom-deps phantom-dep:react-is AI (phantom-deps): react-is is a declared dependency; phantom-dep heuristic fails on bundled output. ai
phantom-deps phantom-dep:unified AI (phantom-deps): unified is a declared dependency; phantom-dep heuristic fails on bundled output. ai
phantom-deps phantom-dep:remark-gfm AI (phantom-deps): remark-gfm is a declared dependency; phantom-dep heuristic fails on bundled output. ai
phantom-deps phantom-dep:remark-math AI (phantom-deps): remark-math is a declared dependency; phantom-dep heuristic fails on bundled output. ai
phantom-deps phantom-dep:remark-parse AI (phantom-deps): remark-parse is a declared dependency; phantom-dep heuristic fails on bundled output. ai

Versions (showing 18 of 18)

Version Deps Published
0.0.38 8 / 2
0.0.37 8 / 2
0.0.36 8 / 2
0.0.35 8 / 2
0.0.34 8 / 2
0.0.33 8 / 2
0.0.32 8 / 2
0.0.31 8 / 2
0.0.30 8 / 2
0.0.29 8 / 2
0.0.28 8 / 2
0.0.27 8 / 2
0.0.26 8 / 2
0.0.25 8 / 2
0.0.24 8 / 2
0.0.23 8 / 2
0.0.22 8 / 2
0.0.21 8 / 2

v0.0.38

1 finding
LOW No provenance attestation provenance

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

v0.0.37

1 finding
LOW No provenance attestation provenance

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

v0.0.36

1 finding
LOW No provenance attestation provenance

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

v0.0.35

1 finding
LOW No provenance attestation provenance

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

v0.0.34

1 finding
LOW No provenance attestation provenance

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

v0.0.33

1 finding
LOW No provenance attestation provenance

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

v0.0.32

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.

v0.0.29

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.

v0.0.28

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.

v0.0.27

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.

v0.0.26

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.

v0.0.25

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.

v0.0.24

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.

v0.0.23

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.

v0.0.22

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.

v0.0.21

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.