@backstage/plugin-proxy-backend
A Backstage backend plugin that helps you set up proxy endpoints in the backend
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): @backstage/types is a legitimate Backstage ecosystem package; phantom-dep finding is a false positive common in monorepo packages where types are used transitively. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo packages do not currently publish with Sigstore provenance; this is a stable characteristic of the package, not a security concern. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.6.13 | 5 / 10 | |
| 0.6.12 | 5 / 10 | |
| 0.6.11 | 5 / 10 | |
| 0.6.10 | 5 / 10 | |
| 0.6.9 | 5 / 10 | |
| 0.6.8 | 5 / 10 | |
| 0.6.7 | 5 / 10 | |
| 0.6.6 | 5 / 10 | |
| 0.6.5 | 5 / 10 | |
| 0.6.4 | 5 / 10 | |
| 0.6.3 | 5 / 10 | |
| 0.6.2 | 5 / 10 |
v0.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
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.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.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.6.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.