@difizen/libro-l10n
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@difizen/mana-app | AI (dependencies): Same @difizen org dependency used across the libro monorepo; stable pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): l10n stub package in a large monorepo; empty entry point and minimal README are expected for this package type. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Localization stub; missing description is consistent across the libro monorepo packages. | ai | |
| phantom-deps | phantom-dep:@difizen/mana-app | AI (phantom-deps): Same org scope; phantom-dep heuristic unreliable for re-export/stub packages in monorepos. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.3.58 | 2 / 0 | |
| 0.3.57 | 2 / 0 | |
| 0.3.56 | 2 / 0 | |
| 0.3.51 | 2 / 0 | |
| 0.3.50 | 2 / 0 | |
| 0.3.49 | 2 / 0 | |
| 0.3.48 | 2 / 0 | |
| 0.3.47 | 2 / 0 | |
| 0.3.43 | 2 / 0 | |
| 0.3.42 | 2 / 0 | |
| 0.3.38 | 2 / 0 | |
| 0.3.37 | 2 / 0 | |
| 0.3.35 | 2 / 0 | |
| 0.3.33 | 2 / 0 | |
| 0.3.32 | 2 / 0 | |
| 0.3.31 | 2 / 0 | |
| 0.3.25 | 2 / 0 |
v0.3.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.50
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.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.42
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.