podlite
Podlite markup language parser — Markdown-compatible, with native support for diagrams, formulas, and custom 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:pod6 | AI (dependencies): Sibling package by same author/purpose (pod6 markup), consistent with podlite's stated function. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adds well-known markdown parsing libs (unified, remark-parse) matching package description. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating common provenance adoption; no other risk signals present. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.0.66 | 7 / 5 | |
| 0.0.65 | 7 / 5 | |
| 0.0.64 | 7 / 5 | |
| 0.0.63 | 7 / 5 | |
| 0.0.62 | 7 / 5 | |
| 0.0.61 | 7 / 5 | |
| 0.0.60 | 7 / 5 | |
| 0.0.59 | 7 / 5 | |
| 0.0.58 | 7 / 5 | |
| 0.0.57 | 7 / 4 | |
| 0.0.56 | 7 / 4 | |
| 0.0.55 | 7 / 4 | |
| 0.0.54 | 7 / 4 | |
| 0.0.53 | 7 / 4 | |
| 0.0.52 | 7 / 4 | |
| 0.0.51 | 7 / 4 | |
| 0.0.50 | 7 / 4 | |
| 0.0.49 | 7 / 4 | |
| 0.0.48 | 7 / 4 | |
| 0.0.47 | 7 / 4 | |
| 0.0.46 | 7 / 4 | |
| 0.0.45 | 7 / 4 | |
| 0.0.44 | 7 / 4 | |
| 0.0.43 | 7 / 4 | |
| 0.0.42 | 7 / 4 | |
| 0.0.41 | 7 / 4 | |
| 0.0.40 | 7 / 4 | |
| 0.0.39 | 7 / 4 | |
| 0.0.38 | 7 / 4 | |
| 0.0.37 | 7 / 4 | |
| 0.0.36 | 7 / 4 | |
| 0.0.35 | 7 / 4 | |
| 0.0.34 | 7 / 4 | |
| 0.0.33 | 7 / 4 | |
| 0.0.32 | 7 / 4 | |
| 0.0.31 | 6 / 4 | |
| 0.0.30 | 6 / 4 | |
| 0.0.29 | 6 / 4 | |
| 0.0.28 | 6 / 4 | |
| 0.0.27 | 6 / 4 | |
| 0.0.26 | 6 / 4 | |
| 0.0.25 | 6 / 4 | |
| 0.0.6 | 6 / 7 | |
| 0.0.2 | 3 / 5 | |
| 0.0.1 | 0 / 0 |
v0.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
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.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.