@difizen/libro-search
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:reflect-metadata | AI (phantom-deps): Known implicit runtime dep in DI-heavy frameworks; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@difizen/libro-common | AI (phantom-deps): Same-org monorepo sibling; likely re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@types/lodash.debounce | AI (phantom-deps): Type-only package; not imported directly by convention. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component packages routinely lack standalone READMEs; not a spam indicator here. | ai |
Versions (showing 51 of 104)
| Version | Deps | Published |
|---|---|---|
| 0.3.58 | 10 / 1 | |
| 0.3.57 | 10 / 1 | |
| 0.3.56 | 10 / 1 | |
| 0.3.55 | 10 / 1 | |
| 0.3.54 | 10 / 1 | |
| 0.3.53 | 10 / 1 | |
| 0.3.52 | 10 / 1 | |
| 0.3.51 | 10 / 1 | |
| 0.3.50 | 10 / 1 | |
| 0.3.49 | 10 / 1 | |
| 0.3.48 | 10 / 1 | |
| 0.3.47 | 10 / 1 | |
| 0.3.46 | 10 / 1 | |
| 0.3.45 | 10 / 1 | |
| 0.3.44 | 10 / 1 | |
| 0.3.43 | 10 / 1 | |
| 0.3.42 | 10 / 1 | |
| 0.3.41 | 10 / 1 | |
| 0.3.40 | 10 / 1 | |
| 0.3.39 | 10 / 1 | |
| 0.3.38 | 10 / 1 | |
| 0.3.37 | 10 / 1 | |
| 0.3.36 | 10 / 1 | |
| 0.3.35 | 10 / 1 | |
| 0.3.34 | 10 / 1 | |
| 0.3.33 | 10 / 1 | |
| 0.3.29 | 10 / 1 | |
| 0.3.28 | 10 / 1 | |
| 0.3.27 | 10 / 1 | |
| 0.3.26 | 10 / 1 | |
| 0.3.25 | 10 / 1 | |
| 0.3.24 | 10 / 1 | |
| 0.3.23 | 10 / 1 | |
| 0.3.22 | 10 / 1 | |
| 0.3.21 | 10 / 1 | |
| 0.3.20 | 10 / 1 | |
| 0.3.19 | 10 / 1 | |
| 0.3.18 | 10 / 1 | |
| 0.3.17 | 10 / 1 | |
| 0.3.16 | 10 / 1 | |
| 0.3.15 | 10 / 1 | |
| 0.3.14 | 10 / 1 | |
| 0.3.13 | 10 / 1 | |
| 0.3.12 | 10 / 1 | |
| 0.3.11 | 10 / 1 | |
| 0.3.10 | 10 / 1 | |
| 0.3.9 | 10 / 1 | |
| 0.3.8 | 10 / 1 | |
| 0.3.7 | 10 / 1 | |
| 0.3.6 | 10 / 1 | |
| 0.3.5 | 10 / 1 |
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.