@backstage/core-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Backstage monorepo packages lack Sigstore provenance; stable across versions. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): First-party Backstage monorepo package; expected dependency for core Backstage libraries. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): First-party Backstage monorepo package; expected dependency for core Backstage libraries. | ai | |
| dependencies | unvetted-dep:@backstage/version-bridge | AI (dependencies): First-party Backstage monorepo package; expected dependency for core Backstage libraries. | ai | |
| dependencies | unvetted-dep:@backstage/ui | AI (dependencies): First-party Backstage monorepo package; unvetted status is a registry artifact, not a security concern for this well-established ecosystem. | ai | |
| dependencies | unvetted-dep:zen-observable | AI (dependencies): zen-observable is a well-known, stable observable library used across many major projects; no security concerns. | ai | |
| phantom-deps | phantom-dep:history | AI (phantom-deps): history is declared in package.json and is a standard React routing dependency; phantom detection is a false positive here. | ai | |
| phantom-deps | phantom-dep:@types/prop-types | AI (phantom-deps): Type declaration package loaded by convention in React projects; phantom detection is expected and benign. | ai | |
| dependencies | unvetted-dep:@backstage/core-plugin-api | AI (dependencies): First-party Backstage monorepo package; expected dependency for core Backstage libraries. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.20.1 | 13 / 17 | |
| 1.20.0 | 13 / 17 | |
| 1.19.5 | 12 / 17 | |
| 1.19.4 | 12 / 17 | |
| 1.19.2 | 12 / 17 | |
| 1.19.1 | 12 / 17 | |
| 1.19.0 | 12 / 17 | |
| 1.18.0 | 12 / 17 | |
| 1.17.1 | 12 / 17 | |
| 1.17.0 | 12 / 17 |
v1.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.1
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.19.0
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.18.0
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.17.1
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.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.