@difizen/libro-core
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:dnd-core | AI (phantom-deps): dnd-core is a transitive peer of react-dnd; declared for version pinning, not a direct import. | ai | |
| phantom-deps | phantom-dep:react-dnd | AI (phantom-deps): react-dnd used via config/peer pattern in this package; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-dnd-html5-backend | AI (phantom-deps): Same react-dnd ecosystem peer pattern; stable false positive. | ai |
Versions (showing 51 of 78)
| Version | Deps | Published |
|---|---|---|
| 0.3.58 | 17 / 4 | |
| 0.3.55 | 17 / 4 | |
| 0.3.49 | 17 / 4 | |
| 0.3.47 | 17 / 4 | |
| 0.3.40 | 17 / 4 | |
| 0.3.37 | 17 / 4 | |
| 0.3.35 | 17 / 4 | |
| 0.3.34 | 17 / 4 | |
| 0.3.33 | 17 / 4 | |
| 0.3.29 | 17 / 4 | |
| 0.3.26 | 17 / 4 | |
| 0.3.21 | 17 / 4 | |
| 0.3.18 | 17 / 4 | |
| 0.3.17 | 17 / 4 | |
| 0.3.16 | 17 / 4 | |
| 0.3.15 | 17 / 4 | |
| 0.3.14 | 17 / 4 | |
| 0.3.13 | 17 / 4 | |
| 0.3.12 | 17 / 4 | |
| 0.3.11 | 17 / 4 | |
| 0.3.10 | 17 / 4 | |
| 0.3.9 | 17 / 4 | |
| 0.3.8 | 17 / 4 | |
| 0.3.7 | 17 / 4 | |
| 0.3.6 | 17 / 4 | |
| 0.3.5 | 17 / 4 | |
| 0.3.4 | 17 / 4 | |
| 0.3.3 | 15 / 2 | |
| 0.3.2 | 15 / 2 | |
| 0.3.1 | 15 / 2 | |
| 0.3.0 | 15 / 2 | |
| 0.2.44 | 15 / 2 | |
| 0.2.43 | 15 / 2 | |
| 0.2.42 | 15 / 2 | |
| 0.2.41 | 15 / 2 | |
| 0.2.40 | 15 / 2 | |
| 0.2.39 | 15 / 2 | |
| 0.2.38 | 15 / 2 | |
| 0.2.36 | 15 / 2 | |
| 0.2.35 | 15 / 2 | |
| 0.2.34 | 15 / 2 | |
| 0.2.33 | 15 / 2 | |
| 0.2.32 | 15 / 2 | |
| 0.2.31 | 15 / 2 | |
| 0.2.30 | 15 / 2 | |
| 0.2.29 | 15 / 2 | |
| 0.2.28 | 15 / 2 | |
| 0.2.27 | 15 / 2 | |
| 0.2.26 | 15 / 2 | |
| 0.2.25 | 15 / 2 | |
| 0.2.24 | 15 / 2 |
v0.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.