@backstage/plugin-signals-react
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@material-ui/core | AI (phantom-deps): @material-ui/core is a declared runtime dependency in Backstage plugin packages; phantom-dep detection fires because it's not directly imported in source but is used transitively/in config. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): @backstage/types is a first-party Backstage monorepo package; no security concern. This disposition is stable across all versions of this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.0.22 | 3 / 8 | |
| 0.0.21 | 3 / 8 | |
| 0.0.20 | 3 / 8 | |
| 0.0.19 | 3 / 8 | |
| 0.0.18 | 3 / 8 | |
| 0.0.17 | 3 / 8 | |
| 0.0.16 | 3 / 8 | |
| 0.0.15 | 3 / 8 | |
| 0.0.14 | 3 / 8 | |
| 0.0.13 | 3 / 8 |
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.