← Home

@difizen/libro-search-code-cell

npm Repository Homepage
4
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

xiaojie.zjserializedowenximolkzhanbabrokun

Keywords

libronotebook

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@difizen/mana-app AI (dependencies): Core difizen ecosystem dependency; stable pattern across all libro packages. ai
dependencies unvetted-dep:@difizen/libro-core AI (dependencies): Sibling monorepo package; consistent across all libro releases. ai
provenance no-provenance AI (provenance): Established monorepo package; lack of provenance is consistent across all 225 versions. ai

Versions (showing 4 of 104)

Version Deps Published
0.1.37 6 / 0
0.1.36 6 / 0
0.1.35 6 / 0
0.1.34 6 / 0

v0.1.37

1 finding
INFO No provenance attestation provenance

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

v0.1.36

1 finding
INFO No provenance attestation provenance

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

v0.1.35

1 finding
INFO No provenance attestation provenance

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

v0.1.34

1 finding
INFO No provenance attestation provenance

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