@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 — the axios compromise (March 2026) relied on exactly this gap.
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 19 of 19)
| 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 |
v0.3.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.