← Home

@difizen/libro-markdown-cell

npm Repository Homepage
8
Versions
—
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

xiaojie.zjserializedowenximolkzhanbabrokun

Keywords

libronotebooktoc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:markdown-it AI (phantom-deps): Config-referenced dep in a build/render pipeline; stable false positive for this package. ai
phantom-deps phantom-dep:@types/markdown-it AI (phantom-deps): Type-only dep loaded by convention; stable false positive. ai
phantom-deps phantom-dep:markdown-it-anchor AI (phantom-deps): Config-referenced dep; stable false positive for this package. ai

Versions (showing 8 of 8)

Version Deps Published
0.3.58 8 / 1
0.3.51 8 / 1
0.3.44 8 / 1
0.3.39 8 / 1
0.3.37 8 / 1
0.3.30 8 / 1
0.3.26 8 / 1
0.3.21 8 / 1

v0.3.58

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.3.51

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.3.44

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.3.39

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.3.37

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.3.30

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.3.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.3.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.