@difizen/libro-shared-model
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance absence is consistent across all versions of this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo package; sparse README/description is a style choice, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentionally empty description across the libro monorepo; not a malice signal. | ai |
Versions (showing 51 of 78)
| Version | Deps | Published |
|---|---|---|
| 0.3.58 | 5 / 1 | |
| 0.3.54 | 5 / 1 | |
| 0.3.53 | 5 / 1 | |
| 0.3.48 | 5 / 1 | |
| 0.3.41 | 5 / 1 | |
| 0.3.33 | 5 / 1 | |
| 0.3.32 | 5 / 1 | |
| 0.3.31 | 5 / 1 | |
| 0.3.30 | 5 / 1 | |
| 0.3.24 | 5 / 1 | |
| 0.3.20 | 5 / 1 | |
| 0.3.18 | 5 / 1 | |
| 0.3.17 | 5 / 1 | |
| 0.3.16 | 5 / 1 | |
| 0.3.15 | 5 / 1 | |
| 0.3.14 | 5 / 1 | |
| 0.3.13 | 5 / 1 | |
| 0.3.12 | 5 / 1 | |
| 0.3.11 | 5 / 1 | |
| 0.3.10 | 5 / 1 | |
| 0.3.9 | 5 / 1 | |
| 0.3.8 | 5 / 1 | |
| 0.3.7 | 5 / 1 | |
| 0.3.6 | 5 / 1 | |
| 0.3.5 | 5 / 1 | |
| 0.3.4 | 5 / 1 | |
| 0.3.3 | 5 / 1 | |
| 0.3.2 | 5 / 1 | |
| 0.3.1 | 5 / 1 | |
| 0.3.0 | 5 / 1 | |
| 0.2.45 | 5 / 1 | |
| 0.2.44 | 5 / 1 | |
| 0.2.43 | 5 / 1 | |
| 0.2.42 | 5 / 1 | |
| 0.2.41 | 5 / 1 | |
| 0.2.40 | 5 / 1 | |
| 0.2.39 | 5 / 1 | |
| 0.2.38 | 5 / 1 | |
| 0.2.37 | 5 / 1 | |
| 0.2.35 | 5 / 1 | |
| 0.2.34 | 5 / 1 | |
| 0.2.33 | 5 / 1 | |
| 0.2.32 | 5 / 1 | |
| 0.2.31 | 5 / 1 | |
| 0.2.30 | 5 / 1 | |
| 0.2.29 | 5 / 1 | |
| 0.2.28 | 5 / 1 | |
| 0.2.27 | 5 / 1 | |
| 0.2.26 | 5 / 1 | |
| 0.2.25 | 5 / 1 | |
| 0.2.24 | 5 / 1 |
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.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.