@backstage/plugin-search-backend-node
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/lunr | AI (dependencies): @types/lunr is the TypeScript types for lunr, a legitimate runtime dependency of this search backend plugin. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared runtime dependency of this package; phantom-dep flag is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/lunr | AI (phantom-deps): @types/lunr is a TypeScript type package loaded by convention alongside lunr; expected pattern for this package. | ai |
Versions (showing 63 of 63)
| Version | Deps | Published |
|---|---|---|
| 1.4.6 | 9 / 4 | |
| 1.4.5 | 9 / 4 | |
| 1.4.4 | 9 / 4 | |
| 1.4.3 | 10 / 4 | |
| 1.4.2 | 10 / 4 | |
| 1.4.1 | 10 / 4 | |
| 1.4.0 | 10 / 4 | |
| 1.3.17 | 10 / 4 | |
| 1.3.16 | 10 / 4 | |
| 1.3.15 | 10 / 4 | |
| 1.3.14 | 10 / 4 | |
| 1.3.13 | 10 / 4 | |
| 1.3.12 | 10 / 4 | |
| 1.3.11 | 10 / 4 | |
| 1.3.10 | 10 / 4 | |
| 1.3.9 | 10 / 4 | |
| 1.3.8 | 10 / 4 | |
| 1.3.7 | 10 / 5 | |
| 1.3.6 | 10 / 5 | |
| 1.3.5 | 11 / 4 | |
| 1.3.4 | 11 / 4 | |
| 1.3.3 | 11 / 4 | |
| 1.3.2 | 11 / 4 | |
| 1.3.1 | 11 / 4 | |
| 1.3.0 | 11 / 4 | |
| 1.2.27 | 12 / 4 | |
| 1.2.26 | 12 / 4 | |
| 1.2.25 | 12 / 4 | |
| 1.2.24 | 12 / 4 | |
| 1.2.23 | 12 / 3 | |
| 1.2.22 | 12 / 3 | |
| 1.2.21 | 12 / 3 | |
| 1.2.20 | 13 / 3 | |
| 1.2.19 | 13 / 3 | |
| 1.2.18 | 13 / 3 | |
| 1.2.17 | 13 / 3 | |
| 1.2.16 | 13 / 3 | |
| 1.2.15 | 13 / 3 | |
| 1.2.14 | 13 / 3 | |
| 1.2.13 | 13 / 3 | |
| 1.2.12 | 13 / 3 | |
| 1.2.11 | 13 / 3 | |
| 1.2.10 | 13 / 3 | |
| 1.2.9 | 13 / 3 | |
| 1.2.8 | 13 / 3 | |
| 1.2.7 | 13 / 3 | |
| 1.2.6 | 13 / 3 | |
| 1.2.5 | 13 / 3 | |
| 1.2.4 | 13 / 3 | |
| 1.2.3 | 13 / 3 | |
| 1.2.2 | 13 / 3 | |
| 1.2.1 | 13 / 3 | |
| 1.2.0 | 13 / 3 | |
| 1.1.4 | 12 / 3 | |
| 1.1.3 | 12 / 3 | |
| 1.1.2 | 12 / 3 | |
| 1.1.1 | 12 / 3 | |
| 1.1.0 | 12 / 3 | |
| 1.0.4 | 13 / 3 | |
| 1.0.3 | 13 / 3 | |
| 1.0.2 | 13 / 3 | |
| 1.0.1 | 13 / 3 | |
| 1.0.0 | 13 / 3 |
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.