@backstage/core-plugin-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): First-party @backstage/* sibling package from the same monorepo; not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): First-party @backstage/* sibling package from the same monorepo; not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): First-party @backstage/* sibling package from the same monorepo; not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@backstage/version-bridge | AI (dependencies): First-party @backstage/* sibling package from the same monorepo; not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@backstage/frontend-plugin-api | AI (dependencies): First-party @backstage/* sibling package from the same monorepo; not a third-party unknown. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Common in monorepo packages; declared for type usage or indirect imports. No malicious signal. | ai | |
| phantom-deps | phantom-dep:history | AI (phantom-deps): Common in monorepo packages; declared for type usage or indirect imports. No malicious signal. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Same-org sibling package; phantom detection is expected for monorepo type-only dependencies. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same-org sibling package; phantom detection is expected for monorepo type-only dependencies. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo packages have not historically published with Sigstore provenance; absence is consistent with all prior versions and not a security risk for this well-known package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.12.6 | 7 / 11 | |
| 1.12.5 | 7 / 11 | |
| 1.12.4 | 7 / 11 | |
| 1.12.3 | 7 / 11 | |
| 1.12.2 | 7 / 11 | |
| 1.12.1 | 7 / 11 | |
| 1.12.0 | 6 / 12 | |
| 1.11.1 | 5 / 11 | |
| 1.11.0 | 5 / 11 | |
| 1.10.9 | 5 / 11 | |
| 1.10.8 | 5 / 11 | |
| 1.10.7 | 5 / 11 |
v1.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.