@backstage/plugin-devtools-common
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): @backstage/types is a first-party Backstage monorepo package; unvetted status reflects pipeline gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-permission-common | AI (dependencies): @backstage/plugin-permission-common is a first-party Backstage monorepo package; unvetted status reflects pipeline gap, not actual risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Common-library packages in large monorepos typically lack standalone README code blocks and keywords; this is a legitimate internal Backstage plugin package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.1.25 | 2 / 1 | |
| 0.1.24 | 2 / 1 | |
| 0.1.23 | 2 / 1 | |
| 0.1.22 | 2 / 1 | |
| 0.1.21 | 2 / 1 | |
| 0.1.20 | 2 / 1 | |
| 0.1.19 | 2 / 1 | |
| 0.1.18 | 2 / 1 | |
| 0.1.17 | 2 / 1 | |
| 0.1.16 | 2 / 1 |
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.