@backstage/plugin-app-backend
A Backstage backend plugin that serves the Backstage frontend 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:knex | AI (dependencies): knex is a well-known SQL query builder; its use in a Backstage backend plugin is expected and legitimate. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. | ai | |
| dependencies | unvetted-dep:express-promise-router | AI (dependencies): Well-known Express middleware; expected dependency for a Backstage backend plugin. | ai | |
| dependencies | unvetted-dep:@backstage/config-loader | AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-app-node | AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-auth-node | AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official Backstage monorepo package; stable dependency for this plugin. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage package with 2055 days history and 107k weekly downloads; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.5.14 | 15 / 7 | |
| 0.5.13 | 16 / 8 | |
| 0.5.12 | 16 / 8 | |
| 0.5.11 | 16 / 8 | |
| 0.5.10 | 16 / 8 | |
| 0.5.9 | 16 / 8 | |
| 0.5.8 | 16 / 8 | |
| 0.5.7 | 16 / 8 | |
| 0.5.6 | 16 / 8 | |
| 0.5.5 | 16 / 8 | |
| 0.5.4 | 16 / 8 | |
| 0.5.3 | 16 / 8 | |
| 0.5.2 | 16 / 8 |
v0.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.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.
v0.5.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.