@backstage/plugin-search-backend
The Backstage backend plugin that provides your backstage app with 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Official @backstage/* sibling package from the same monorepo; not a third-party unknown dependency. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official @backstage/* sibling package from the same monorepo; not a third-party unknown dependency. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-search-common | AI (dependencies): Official @backstage/* sibling package from the same monorepo; not a third-party unknown dependency. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-permission-node | AI (dependencies): Official @backstage/* sibling package from the same monorepo; not a third-party unknown dependency. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-permission-common | AI (dependencies): Official @backstage/* sibling package from the same monorepo; not a third-party unknown dependency. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-search-backend-node | AI (dependencies): Official @backstage/* sibling package from the same monorepo; not a third-party unknown dependency. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-packages commonly lack standalone README code blocks and keywords; not a spam indicator for this established Backstage plugin. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage monorepo package with 1595 versions; absence of Sigstore provenance is consistent with its publishing history. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.1.2 | 14 / 7 | |
| 2.1.1 | 15 / 7 | |
| 2.0.9 | 16 / 6 | |
| 2.0.7 | 16 / 6 | |
| 2.0.6 | 16 / 6 | |
| 2.0.5 | 16 / 6 | |
| 2.0.4 | 16 / 6 | |
| 2.0.3 | 16 / 6 | |
| 2.0.2 | 16 / 6 |
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.