@backstage/plugin-devtools-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/cli-common | AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin. | ai | |
| dependencies | unvetted-dep:express-promise-router | AI (dependencies): Well-known, widely-used Express middleware; no security concerns. | ai | |
| dependencies | unvetted-dep:@backstage/config-loader | AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-devtools-common | AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-permission-node | AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-permission-common | AI (dependencies): Official Backstage monorepo sibling package; legitimate dependency for this plugin. | ai | |
| phantom-deps | phantom-dep:yn | AI (phantom-deps): Declared in package.json as a runtime dep; phantom detection is a false positive for monorepo config usage patterns. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Declared in package.json as a runtime dep; phantom detection is a false positive for monorepo config usage patterns. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Official Backstage sibling package; phantom detection false positive for monorepo indirect usage. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-permission-node | AI (phantom-deps): Official Backstage sibling package; phantom detection false positive for monorepo indirect usage. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.5.17 | 17 / 8 | |
| 0.5.16 | 19 / 8 | |
| 0.5.15 | 19 / 8 | |
| 0.5.14 | 19 / 8 | |
| 0.5.13 | 20 / 8 | |
| 0.5.12 | 20 / 8 | |
| 0.5.11 | 20 / 8 | |
| 0.5.10 | 20 / 8 | |
| 0.5.9 | 20 / 8 | |
| 0.5.8 | 20 / 8 | |
| 0.5.7 | 20 / 8 | |
| 0.5.6 | 20 / 8 | |
| 0.5.5 | 20 / 8 |
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.