@backstage/app-defaults
Provides the default wiring of a Backstage App
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/theme | AI (dependencies): Official Backstage monorepo package; legitimate and widely used. Unvetted status reflects registry gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@material-ui/icons | AI (dependencies): @material-ui/icons is a well-established Material UI package with millions of weekly downloads. No risk. | ai | |
| dependencies | unvetted-dep:@backstage/core-app-api | AI (dependencies): Official Backstage monorepo package; legitimate and widely used. Unvetted status reflects registry gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/core-components | AI (dependencies): Official Backstage monorepo package; legitimate and widely used. Unvetted status reflects registry gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/core-plugin-api | AI (dependencies): Official Backstage monorepo package; legitimate and widely used. Unvetted status reflects registry gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-permission-react | AI (dependencies): Official Backstage monorepo package; legitimate and widely used. Unvetted status reflects registry gap, not actual risk. | ai | |
| provenance | no-provenance | AI (provenance): Backstage packages historically do not publish with Sigstore provenance. Package identity is well-established via 1600+ days of history and 107k weekly downloads. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.7.8 | 7 / 8 | |
| 1.7.7 | 7 / 8 | |
| 1.7.6 | 7 / 8 | |
| 1.7.5 | 7 / 8 | |
| 1.7.4 | 7 / 8 | |
| 1.7.3 | 7 / 8 | |
| 1.7.2 | 7 / 8 | |
| 1.7.1 | 7 / 8 | |
| 1.7.0 | 7 / 8 | |
| 1.6.5 | 7 / 8 | |
| 1.6.4 | 7 / 8 | |
| 1.6.3 | 7 / 8 | |
| 1.6.2 | 7 / 8 |
v1.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
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.6.4
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.6.3
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.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.