@backstage/frontend-app-api
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/version-bridge | AI (dependencies): @backstage/version-bridge is a legitimate same-org Backstage package; it is a stable dependency across all Backstage frontend packages. | ai | |
| phantom-deps | phantom-dep:@backstage/errors | AI (phantom-deps): Same-org @backstage package used transitively in a monorepo build artifact; not indicative of risk. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is declared as a runtime dep and referenced in config schema; phantom detection may miss indirect usage patterns in Backstage monorepo packages. | ai | |
| phantom-deps | phantom-dep:@backstage/core-app-api | AI (phantom-deps): Same-org Backstage dependency; indirect usage via type re-exports or config is expected in the Backstage monorepo pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Backstage monorepo packages routinely lack keywords, detailed READMEs, and descriptions on npm — this is a structural pattern, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:@backstage/core-plugin-api | AI (phantom-deps): Same-org Backstage dependency; indirect usage is expected in the Backstage monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/frontend-defaults | AI (phantom-deps): Same-org Backstage dependency; indirect usage is expected in the Backstage monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/version-bridge | AI (phantom-deps): Same-org Backstage dependency; indirect usage is expected in the Backstage monorepo pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Backstage monorepo packages commonly omit npm descriptions; not indicative of malicious intent for this well-established package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.16.3 | 11 / 11 | |
| 0.16.2 | 11 / 11 | |
| 0.16.1 | 11 / 11 | |
| 0.16.0 | 11 / 11 | |
| 0.15.0 | 10 / 10 | |
| 0.14.1 | 10 / 10 | |
| 0.14.0 | 10 / 10 | |
| 0.13.3 | 10 / 10 | |
| 0.13.2 | 10 / 10 | |
| 0.13.1 | 10 / 10 | |
| 0.13.0 | 10 / 10 | |
| 0.12.0 | 10 / 10 | |
| 0.11.4 | 10 / 9 | |
| 0.11.3 | 10 / 9 | |
| 0.11.2 | 10 / 9 |
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.