@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, so a manually published version cannot be tied back to a reviewed commit.
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 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1.1.25 | 12 / 11 | |
| 1.1.24 | 12 / 11 | |
| 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 | |
| 1.1.9 | 11 / 11 | |
| 1.1.8 | 11 / 11 | |
| 1.1.7 | 11 / 11 | |
| 1.1.6 | 11 / 11 | |
| 1.1.5 | 11 / 11 | |
| 1.1.4 | 11 / 11 | |
| 1.1.3 | 11 / 11 | |
| 1.1.2 | 11 / 11 | |
| 1.1.1 | 12 / 7 | |
| 1.1.0 | 12 / 7 | |
| 1.0.37 | 12 / 7 | |
| 1.0.36 | 12 / 7 | |
| 1.0.35 | 12 / 7 | |
| 1.0.34 | 12 / 7 | |
| 1.0.33 | 12 / 7 | |
| 1.0.32 | 12 / 7 | |
| 1.0.31 | 12 / 7 | |
| 1.0.30 | 12 / 7 | |
| 1.0.29 | 12 / 7 | |
| 1.0.28 | 12 / 7 | |
| 1.0.27 | 12 / 7 | |
| 1.0.26 | 12 / 7 | |
| 1.0.25 | 12 / 7 | |
| 1.0.24 | 12 / 7 | |
| 1.0.23 | 12 / 7 | |
| 1.0.22 | 12 / 7 |
v1.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
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.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
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.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.