@difizen/libro-output
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has strong track record (83 approved, 0 rejected); monorepo release cadence explains gaps. | ai | |
| phantom-deps | phantom-dep:@difizen/mana-l10n | AI (phantom-deps): Same-org dependency declared but not directly imported; consistent pattern across this monorepo's packages. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-established, widely-used library appropriate for a notebook output renderer; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; provenance not used across the difizen/libro ecosystem. | ai | |
| phantom-deps | phantom-dep:markdown-it | AI (phantom-deps): markdown-it is a declared runtime dep; phantom-dep is a false positive here. | ai |
Versions (showing 85 of 85)
| Version | Deps | Published |
|---|---|---|
| 0.3.58 | 7 / 2 | |
| 0.3.56 | 7 / 2 | |
| 0.3.54 | 7 / 2 | |
| 0.3.53 | 7 / 2 | |
| 0.3.52 | 7 / 2 | |
| 0.3.49 | 7 / 2 | |
| 0.3.38 | 6 / 2 | |
| 0.3.37 | 6 / 2 | |
| 0.3.35 | 6 / 2 | |
| 0.3.29 | 6 / 2 | |
| 0.3.28 | 6 / 2 | |
| 0.3.25 | 6 / 2 | |
| 0.3.24 | 6 / 2 | |
| 0.3.23 | 5 / 2 | |
| 0.3.22 | 5 / 2 | |
| 0.3.21 | 5 / 2 | |
| 0.3.20 | 5 / 2 | |
| 0.3.19 | 5 / 2 | |
| 0.3.18 | 5 / 2 | |
| 0.3.17 | 5 / 2 | |
| 0.3.16 | 5 / 2 | |
| 0.3.15 | 5 / 2 | |
| 0.3.14 | 5 / 2 | |
| 0.3.13 | 5 / 2 | |
| 0.3.12 | 5 / 2 | |
| 0.3.11 | 5 / 2 | |
| 0.3.10 | 5 / 2 | |
| 0.3.9 | 5 / 2 | |
| 0.3.8 | 5 / 2 | |
| 0.3.7 | 5 / 2 | |
| 0.3.6 | 5 / 2 | |
| 0.3.5 | 5 / 2 | |
| 0.3.4 | 5 / 2 | |
| 0.3.3 | 5 / 2 | |
| 0.3.2 | 5 / 2 | |
| 0.3.1 | 5 / 2 | |
| 0.3.0 | 5 / 2 | |
| 0.2.45 | 5 / 2 | |
| 0.2.44 | 5 / 2 | |
| 0.2.43 | 5 / 2 | |
| 0.2.42 | 5 / 2 | |
| 0.2.41 | 5 / 2 | |
| 0.2.40 | 5 / 2 | |
| 0.2.39 | 5 / 2 | |
| 0.2.38 | 5 / 2 | |
| 0.2.37 | 5 / 2 | |
| 0.2.35 | 5 / 2 | |
| 0.2.34 | 5 / 2 | |
| 0.2.33 | 5 / 2 | |
| 0.2.32 | 5 / 2 | |
| 0.2.31 | 5 / 2 | |
| 0.2.30 | 5 / 2 | |
| 0.2.29 | 5 / 2 | |
| 0.2.28 | 5 / 2 | |
| 0.2.27 | 5 / 2 | |
| 0.2.26 | 5 / 2 | |
| 0.2.25 | 5 / 2 | |
| 0.2.24 | 5 / 2 | |
| 0.2.23 | 5 / 2 | |
| 0.2.22 | 5 / 2 | |
| 0.2.21 | 5 / 2 | |
| 0.2.20 | 5 / 2 | |
| 0.2.19 | 5 / 2 | |
| 0.2.18 | 5 / 2 | |
| 0.2.17 | 5 / 2 | |
| 0.2.16 | 5 / 2 | |
| 0.2.15 | 5 / 2 | |
| 0.2.14 | 5 / 2 | |
| 0.2.13 | 5 / 2 | |
| 0.2.12 | 5 / 2 | |
| 0.2.11 | 5 / 2 | |
| 0.2.10 | 5 / 2 | |
| 0.2.9 | 5 / 2 | |
| 0.2.8 | 5 / 2 | |
| 0.2.7 | 5 / 2 | |
| 0.2.6 | 5 / 2 | |
| 0.2.5 | 5 / 2 | |
| 0.2.4 | 5 / 2 | |
| 0.2.3 | 5 / 2 | |
| 0.2.2 | 5 / 2 | |
| 0.2.1 | 5 / 2 | |
| 0.1.37 | 5 / 2 | |
| 0.1.36 | 5 / 2 | |
| 0.1.35 | 5 / 2 | |
| 0.1.34 | 5 / 2 |
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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v0.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.