@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 4 of 104)
| Version | Deps | Published |
|---|---|---|
| 0.1.37 | 10 / 1 | |
| 0.1.36 | 10 / 1 | |
| 0.1.35 | 10 / 1 | |
| 0.1.34 | 10 / 1 |
v0.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.