@backstage/plugin-gateway-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Backstage monorepo packages commonly omit descriptions; not a malware indicator for this well-established scoped package. | ai | |
| provenance | no-provenance | AI (provenance): Lack of provenance is common across npm; no other signals suggest tampering for this official Backstage package. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Express is a legitimate runtime dependency declared in package.json; Backstage backend plugins use it for middleware without always having a direct top-level import. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.1.5 | 5 / 7 | |
| 1.1.4 | 5 / 7 | |
| 1.1.3 | 5 / 7 | |
| 1.1.2 | 5 / 7 | |
| 1.1.1 | 5 / 7 | |
| 1.1.0 | 5 / 7 | |
| 1.0.6 | 5 / 7 | |
| 1.0.5 | 5 / 7 | |
| 1.0.4 | 5 / 7 | |
| 1.0.3 | 5 / 7 | |
| 1.0.2 | 5 / 7 | |
| 1.0.1 | 5 / 7 |
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.
v1.0.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.