@backstage/plugin-auth-backend-module-guest-provider
The guest-provider backend module for the auth plugin.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official Backstage monorepo package; unvetted only due to system review gap, not suspicious. | ai | |
| dependencies | unvetted-dep:@backstage/catalog-model | AI (dependencies): Official Backstage monorepo package; unvetted only due to system review gap, not suspicious. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-auth-node | AI (dependencies): Official Backstage monorepo package; unvetted only due to system review gap, not suspicious. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official Backstage monorepo package; unvetted only due to system review gap, not suspicious. | ai | |
| phantom-deps | phantom-dep:passport-oauth2 | AI (phantom-deps): passport-oauth2 is declared as a runtime dep and referenced in config schema; pattern is consistent with Backstage module conventions. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.2.19 | 5 / 4 | |
| 0.2.18 | 5 / 4 | |
| 0.2.17 | 5 / 4 | |
| 0.2.16 | 5 / 4 | |
| 0.2.15 | 5 / 4 | |
| 0.2.14 | 5 / 4 | |
| 0.2.13 | 5 / 4 | |
| 0.2.12 | 5 / 4 | |
| 0.2.11 | 5 / 4 | |
| 0.2.10 | 5 / 4 | |
| 0.2.9 | 5 / 4 | |
| 0.2.8 | 5 / 4 |
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.