@difizen/libro-search-code-cell
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:@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 51 of 104)
| Version | Deps | Published |
|---|---|---|
| 0.3.58 | 6 / 0 | |
| 0.3.57 | 6 / 0 | |
| 0.3.56 | 6 / 0 | |
| 0.3.55 | 6 / 0 | |
| 0.3.54 | 6 / 0 | |
| 0.3.53 | 6 / 0 | |
| 0.3.52 | 6 / 0 | |
| 0.3.51 | 6 / 0 | |
| 0.3.50 | 6 / 0 | |
| 0.3.49 | 6 / 0 | |
| 0.3.48 | 6 / 0 | |
| 0.3.47 | 6 / 0 | |
| 0.3.46 | 6 / 0 | |
| 0.3.45 | 6 / 0 | |
| 0.3.44 | 6 / 0 | |
| 0.3.43 | 6 / 0 | |
| 0.3.42 | 6 / 0 | |
| 0.3.41 | 6 / 0 | |
| 0.3.40 | 6 / 0 | |
| 0.3.39 | 6 / 0 | |
| 0.3.38 | 6 / 0 | |
| 0.3.37 | 6 / 0 | |
| 0.3.36 | 6 / 0 | |
| 0.3.35 | 6 / 0 | |
| 0.3.34 | 6 / 0 | |
| 0.3.33 | 6 / 0 | |
| 0.3.29 | 6 / 0 | |
| 0.3.28 | 6 / 0 | |
| 0.3.27 | 6 / 0 | |
| 0.3.26 | 6 / 0 | |
| 0.3.25 | 6 / 0 | |
| 0.3.24 | 6 / 0 | |
| 0.3.23 | 6 / 0 | |
| 0.3.22 | 6 / 0 | |
| 0.3.21 | 6 / 0 | |
| 0.3.20 | 6 / 0 | |
| 0.3.19 | 6 / 0 | |
| 0.3.18 | 6 / 0 | |
| 0.3.17 | 6 / 0 | |
| 0.3.16 | 6 / 0 | |
| 0.3.15 | 6 / 0 | |
| 0.3.14 | 6 / 0 | |
| 0.3.13 | 6 / 0 | |
| 0.3.12 | 6 / 0 | |
| 0.3.11 | 6 / 0 | |
| 0.3.10 | 6 / 0 | |
| 0.3.9 | 6 / 0 | |
| 0.3.8 | 6 / 0 | |
| 0.3.7 | 6 / 0 | |
| 0.3.6 | 6 / 0 | |
| 0.3.5 | 6 / 0 |
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ximolk) than the most recent previously approved version (brokun) on 2025-03-05, but ximolk is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ximolk) than the most recent previously approved version (brokun) on 2025-03-05, but ximolk is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.