@backstage/plugin-auth-react
Web library 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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Backstage monorepo sub-packages routinely have minimal READMEs and no keywords; documentation lives in the main repo. Not a spam indicator for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage package with 596 versions and 87k weekly downloads; lack of provenance is consistent with its publication history and not a risk signal here. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.1.29 | 5 / 9 | |
| 0.1.28 | 5 / 10 | |
| 0.1.27 | 5 / 10 | |
| 0.1.26 | 5 / 10 | |
| 0.1.25 | 5 / 10 | |
| 0.1.24 | 5 / 10 | |
| 0.1.23 | 5 / 10 | |
| 0.1.22 | 5 / 10 | |
| 0.1.21 | 5 / 10 | |
| 0.1.20 | 5 / 10 | |
| 0.1.19 | 5 / 10 | |
| 0.1.18 | 5 / 10 | |
| 0.1.17 | 5 / 10 | |
| 0.1.16 | 5 / 10 | |
| 0.1.15 | 5 / 10 | |
| 0.1.14 | 5 / 10 | |
| 0.1.13 | 5 / 10 | |
| 0.1.12 | 5 / 10 | |
| 0.1.11 | 5 / 10 | |
| 0.1.10 | 5 / 10 | |
| 0.1.9 | 5 / 10 | |
| 0.1.8 | 5 / 10 | |
| 0.1.7 | 5 / 10 | |
| 0.1.6 | 6 / 6 | |
| 0.1.5 | 6 / 6 | |
| 0.1.4 | 6 / 6 | |
| 0.1.3 | 6 / 6 | |
| 0.1.2 | 6 / 6 | |
| 0.1.1 | 6 / 6 | |
| 0.1.0 | 6 / 6 | |
| 0.0.3 | 6 / 5 | |
| 0.0.2 | 6 / 5 | |
| 0.0.1 | 6 / 5 |
v0.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.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.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.