@backstage/plugin-signals-backend
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:yn | AI (phantom-deps): Utility library used in Backstage backend plugins; phantom-dep pattern is stable. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): Standard logging library in Backstage backend; phantom-dep pattern is stable. | ai | |
| phantom-deps | phantom-dep:http-proxy-middleware | AI (phantom-deps): Express middleware used in backend plugin; phantom-dep pattern is stable. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-auth-node | AI (phantom-deps): Same-org Backstage dependency; phantom-dep pattern is stable for plugins. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Same-org @backstage scoped package; phantom dep in monorepo sub-packages is expected and not a risk signal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Backstage monorepo sub-packages routinely omit standalone descriptions; not a risk signal for this established package. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same-org @backstage scoped package; phantom dep in monorepo sub-packages is expected and not a risk signal. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-signals-node | AI (phantom-deps): Same-org @backstage scoped package; phantom dep in monorepo sub-packages is expected and not a risk signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-packages commonly lack standalone README/keywords/description; not indicative of spam or malice for this well-established Backstage plugin. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.3.15 | 8 / 10 | |
| 0.3.14 | 9 / 10 | |
| 0.3.13 | 9 / 10 | |
| 0.3.12 | 9 / 10 | |
| 0.3.11 | 9 / 10 | |
| 0.3.10 | 9 / 10 | |
| 0.3.9 | 13 / 11 | |
| 0.3.8 | 13 / 11 | |
| 0.3.7 | 13 / 11 | |
| 0.3.6 | 13 / 11 | |
| 0.3.5 | 13 / 11 | |
| 0.3.4 | 13 / 11 |
v0.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.