@backstage/plugin-search
The Backstage 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@material-ui/icons | AI (dependencies): @material-ui/icons is a well-known, widely-used Material UI v4 package; a standard and expected dependency for Backstage frontend plugins. | ai | |
| dependencies | unvetted-dep:@backstage/version-bridge | AI (dependencies): @backstage/version-bridge is a first-party Backstage utility package; stable and expected in the Backstage ecosystem. | ai | |
| phantom-deps | phantom-dep:@backstage/ui | AI (phantom-deps): Same-org Backstage package; phantom dep pattern is common in Backstage monorepo plugins where transitive usage occurs. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Same-org Backstage package; phantom dep pattern is common in Backstage monorepo plugins where transitive usage occurs. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage package (1984 days, 87.9k weekly downloads) from official GitHub repo; lack of provenance is not disqualifying here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.7.4 | 15 / 13 | |
| 1.7.3 | 15 / 13 | |
| 1.7.2 | 15 / 13 | |
| 1.7.1 | 14 / 13 | |
| 1.7.0 | 14 / 13 | |
| 1.6.1 | 13 / 13 | |
| 1.6.0 | 13 / 13 | |
| 1.5.3 | 13 / 13 | |
| 1.5.2 | 13 / 13 | |
| 1.5.1 | 13 / 13 | |
| 1.5.0 | 14 / 13 | |
| 1.4.31 | 14 / 13 | |
| 1.4.30 | 14 / 13 | |
| 1.4.29 | 14 / 13 | |
| 1.4.28 | 14 / 13 | |
| 1.4.27 | 14 / 13 | |
| 1.4.26 | 14 / 13 |
v1.7.4
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.