@backstage/plugin-auth-backend-module-aws-alb-provider
The aws-alb provider module for the Backstage auth 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/plugin-auth-backend | AI (phantom-deps): Backstage plugin modules commonly declare the parent plugin as a dependency for type compatibility without directly importing it. This is a stable pattern in the Backstage monorepo. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official Backstage monorepo package; well-established, high-download ecosystem dependency. Unvetted status is a registry coverage gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-auth-node | AI (dependencies): Official Backstage monorepo package; well-established ecosystem dependency. Unvetted status is a registry coverage gap. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official Backstage monorepo package; well-established ecosystem dependency. Unvetted status is a registry coverage gap. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-auth-backend | AI (dependencies): Official Backstage monorepo package; well-established ecosystem dependency. Unvetted status is a registry coverage gap. | ai | |
| dependencies | unvetted-dep:node-cache | AI (dependencies): node-cache is a popular, stable npm caching library with millions of downloads. No known security concerns. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.4.16 | 7 / 6 | |
| 0.4.15 | 7 / 6 | |
| 0.4.14 | 7 / 6 | |
| 0.4.13 | 7 / 6 | |
| 0.4.12 | 7 / 6 | |
| 0.4.11 | 7 / 6 | |
| 0.4.10 | 7 / 6 | |
| 0.4.9 | 7 / 6 | |
| 0.4.8 | 7 / 6 | |
| 0.4.7 | 7 / 6 | |
| 0.4.6 | 7 / 6 | |
| 0.4.5 | 7 / 6 | |
| 0.4.4 | 7 / 6 | |
| 0.4.3 | 7 / 6 |
v0.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.