@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, 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/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 51 of 59)
| Version | Deps | Published |
|---|---|---|
| 1.7.10 | 8 / 8 | |
| 1.7.9 | 8 / 8 | |
| 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 | |
| 1.6.1 | 7 / 8 | |
| 1.6.0 | 7 / 8 | |
| 1.5.17 | 7 / 8 | |
| 1.5.16 | 7 / 8 | |
| 1.5.15 | 7 / 8 | |
| 1.5.14 | 7 / 8 | |
| 1.5.13 | 7 / 8 | |
| 1.5.12 | 7 / 8 | |
| 1.5.11 | 7 / 5 | |
| 1.5.10 | 7 / 5 | |
| 1.5.9 | 7 / 5 | |
| 1.5.8 | 7 / 5 | |
| 1.5.7 | 7 / 5 | |
| 1.5.6 | 7 / 5 | |
| 1.5.5 | 7 / 5 | |
| 1.5.4 | 7 / 5 | |
| 1.5.3 | 7 / 5 | |
| 1.5.2 | 7 / 5 | |
| 1.5.1 | 7 / 5 | |
| 1.5.0 | 7 / 5 | |
| 1.4.7 | 7 / 5 | |
| 1.4.6 | 7 / 5 | |
| 1.4.5 | 7 / 5 | |
| 1.4.4 | 7 / 5 | |
| 1.4.3 | 7 / 5 | |
| 1.4.2 | 7 / 6 | |
| 1.4.1 | 7 / 6 | |
| 1.4.0 | 7 / 6 | |
| 1.3.1 | 7 / 6 | |
| 1.3.0 | 7 / 6 | |
| 1.2.1 | 7 / 6 | |
| 1.2.0 | 7 / 6 | |
| 1.1.0 | 7 / 6 | |
| 1.0.10 | 7 / 6 | |
| 1.0.9 | 7 / 6 | |
| 1.0.8 | 7 / 6 |
v1.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
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.5.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.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
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.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.