@backstage/plugin-search-backend-module-elasticsearch
A module for the search backend that implements search using ElasticSearch
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:elastic-builder | AI (dependencies): elastic-builder is a well-known Elasticsearch query builder library; appropriate dependency for this search backend module. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official Backstage package from the same monorepo; legitimate core dependency. | ai | |
| dependencies | unvetted-dep:@opensearch-project/opensearch | AI (dependencies): Official OpenSearch client from the opensearch-project org; appropriate for an Elasticsearch/OpenSearch backend module. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-search-common | AI (dependencies): Official Backstage package from the same monorepo; legitimate shared types dependency. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-search-backend-node | AI (dependencies): Official Backstage package from the same monorepo; legitimate core dependency for search backend modules. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; short README and no keywords are expected for Backstage plugin modules that rely on the main project documentation. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.8.3 | 10 / 5 | |
| 1.8.2 | 11 / 5 | |
| 1.8.1 | 11 / 5 | |
| 1.8.0 | 11 / 5 | |
| 1.7.9 | 11 / 5 | |
| 1.7.8 | 11 / 5 | |
| 1.7.7 | 11 / 4 | |
| 1.7.6 | 11 / 4 | |
| 1.7.5 | 11 / 4 | |
| 1.7.4 | 11 / 4 | |
| 1.7.3 | 11 / 4 | |
| 1.7.2 | 11 / 4 |
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.