@podlite/markdown
Bidirectional Markdown support for Podlite — parse .md files, embed Markdown blocks
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.0.46 | 8 / 2 | |
| 0.0.45 | 8 / 2 | |
| 0.0.44 | 8 / 2 | |
| 0.0.43 | 8 / 2 | |
| 0.0.42 | 8 / 2 | |
| 0.0.41 | 8 / 2 | |
| 0.0.40 | 8 / 2 | |
| 0.0.39 | 8 / 2 | |
| 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 | |
| 0.0.20 | 8 / 2 | |
| 0.0.19 | 8 / 2 | |
| 0.0.18 | 8 / 2 | |
| 0.0.17 | 8 / 2 | |
| 0.0.16 | 8 / 2 | |
| 0.0.15 | 8 / 2 | |
| 0.0.14 | 8 / 2 | |
| 0.0.13 | 8 / 2 | |
| 0.0.12 | 8 / 2 | |
| 0.0.5 | 7 / 2 |
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.