← Home

@difizen/libro-language-client

npm Repository Homepage
13
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

libronotebook

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): No provenance across all libro packages; stable false positive for this ecosystem. ai
npm-metadata no-description AI (npm-metadata): Part of the difizen/libro monorepo; missing description is a cosmetic issue, not a malware indicator. ai
publish-pattern dormant-publish AI (publish-pattern): Large established monorepo with 210 versions; publisher has clean track record; no code changes from prior approved version. ai
dependencies unvetted-dep:@difizen/vscode-languageserver-protocol AI (dependencies): Same @difizen org/monorepo as the publishing package; not a third-party risk. ai

Versions (showing 13 of 13)

Version Deps Published
0.3.58 13 / 3
0.3.57 13 / 3
0.3.50 13 / 3
0.3.48 13 / 3
0.3.43 13 / 3
0.3.42 13 / 3
0.3.41 13 / 3
0.3.39 13 / 3
0.3.37 13 / 3
0.3.34 13 / 3
0.3.22 13 / 3
0.3.21 13 / 3
0.3.19 13 / 3

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

1 finding
LOW No provenance attestation provenance

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

v0.3.50

1 finding
LOW No provenance attestation provenance

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

v0.3.48

1 finding
LOW No provenance attestation provenance

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

v0.3.43

1 finding
LOW No provenance attestation provenance

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

v0.3.42

1 finding
LOW No provenance attestation provenance

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

v0.3.41

1 finding
LOW No provenance attestation provenance

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

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

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

v0.3.19

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.