@backstage/plugin-auth-backend-module-vmware-cloud-provider
The vmware-cloud-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance attestation is not yet standard practice; absence is not a security signal for established monorepo packages. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-auth-node | AI (dependencies): Core Backstage monorepo package; same org scope. Stable false positive. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Core Backstage monorepo package; same org scope. Stable false positive. | ai | |
| dependencies | unvetted-dep:@types/passport-oauth2 | AI (dependencies): DefinitelyTyped package for passport-oauth2; well-known type declaration package, not a risk. | ai | |
| dependencies | unvetted-dep:@backstage/catalog-model | AI (dependencies): Core Backstage monorepo package; same org scope as this package. Stable false positive for all @backstage/* packages. | ai | |
| phantom-deps | phantom-dep:@backstage/catalog-model | AI (phantom-deps): Same-org monorepo dependency; may be used transitively or via type-only imports. Expected pattern in Backstage monorepo. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-packages commonly lack standalone README code blocks and keywords; not indicative of spam for @backstage/* packages. | ai | |
| phantom-deps | phantom-dep:@types/passport-oauth2 | AI (phantom-deps): Type declaration packages are not directly imported at runtime; this is expected behavior for @types/* packages. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.5.16 | 6 / 9 | |
| 0.5.15 | 6 / 9 | |
| 0.5.14 | 6 / 9 | |
| 0.5.13 | 6 / 9 | |
| 0.5.12 | 6 / 9 | |
| 0.5.11 | 6 / 9 | |
| 0.5.10 | 6 / 9 | |
| 0.5.9 | 6 / 9 | |
| 0.5.8 | 6 / 9 | |
| 0.5.7 | 6 / 9 | |
| 0.5.6 | 6 / 9 | |
| 0.5.5 | 6 / 9 | |
| 0.5.4 | 6 / 9 | |
| 0.5.3 | 6 / 9 | |
| 0.5.2 | 6 / 9 | |
| 0.5.1 | 6 / 9 | |
| 0.5.0 | 6 / 9 | |
| 0.4.3 | 6 / 8 | |
| 0.4.2 | 6 / 8 | |
| 0.4.1 | 6 / 8 | |
| 0.4.0 | 6 / 8 | |
| 0.3.0 | 6 / 8 | |
| 0.2.5 | 6 / 8 | |
| 0.2.4 | 6 / 8 | |
| 0.2.3 | 6 / 8 | |
| 0.2.2 | 6 / 8 | |
| 0.2.1 | 6 / 8 | |
| 0.2.0 | 6 / 8 | |
| 0.1.10 | 6 / 8 | |
| 0.1.9 | 6 / 8 | |
| 0.1.8 | 6 / 8 | |
| 0.1.7 | 6 / 8 | |
| 0.1.6 | 6 / 8 | |
| 0.1.5 | 6 / 8 | |
| 0.1.4 | 6 / 8 | |
| 0.1.3 | 6 / 8 | |
| 0.1.2 | 6 / 8 | |
| 0.1.1 | 6 / 8 | |
| 0.1.0 | 7 / 8 |
v0.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
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.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.