@backstage/dev-utils
Utilities for developing Backstage plugins.
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:@backstage/ui | AI (dependencies): Official Backstage monorepo package; unvetted status reflects review system gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/theme | AI (dependencies): Official Backstage monorepo package; unvetted status reflects review system gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@material-ui/icons | AI (dependencies): Well-established Material UI package with millions of downloads; not a risk for this package. | ai | |
| dependencies | unvetted-dep:@backstage/app-defaults | AI (dependencies): Official Backstage monorepo package; unvetted status reflects review system gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/core-app-api | AI (dependencies): Official Backstage monorepo package; unvetted status reflects review system gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/catalog-model | AI (dependencies): Official Backstage monorepo package; unvetted status reflects review system gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/core-components | AI (dependencies): Official Backstage monorepo package; unvetted status reflects review system gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/core-plugin-api | AI (dependencies): Official Backstage monorepo package; unvetted status reflects review system gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/integration-react | AI (dependencies): Official Backstage monorepo package; unvetted status reflects review system gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-react | AI (dependencies): Official Backstage monorepo package; unvetted status reflects review system gap, not actual risk. | ai | |
| phantom-deps | phantom-dep:@backstage/theme | AI (phantom-deps): Common in large monorepos; @backstage/theme is a legitimate same-org dependency with no security implications. | ai | |
| provenance | no-provenance | AI (provenance): Backstage packages historically published without Sigstore provenance; not a risk signal for this established package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.23 | 12 / 11 | |
| 1.1.22 | 12 / 11 | |
| 1.1.21 | 12 / 11 | |
| 1.1.20 | 12 / 11 | |
| 1.1.19 | 12 / 11 | |
| 1.1.18 | 12 / 11 | |
| 1.1.17 | 12 / 11 | |
| 1.1.16 | 12 / 11 | |
| 1.1.15 | 11 / 11 | |
| 1.1.14 | 11 / 11 | |
| 1.1.13 | 11 / 11 | |
| 1.1.12 | 11 / 11 | |
| 1.1.11 | 11 / 11 | |
| 1.1.10 | 11 / 11 |
v1.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
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.1.11
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.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.