@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 — 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 |
|---|---|---|---|---|
| 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 38 of 38)
| 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 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 findingPackage 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
1 findingPackage 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.