@frontegg/react
<br /> <div align="center"> <img src="https://fronteggstuff.blob.core.windows.net/frongegg-logos/logo-transparent.png" alt="Frontegg Logo" width="400" height="90">
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): Established vendor package; lack of provenance is consistent across all prior versions. | ai |
Versions (showing 91 of 91)
| Version | Deps | Published |
|---|---|---|
| 7.13.11 | 2 / 0 | |
| 7.13.10 | 2 / 0 | |
| 7.13.9 | 2 / 0 | |
| 7.13.8 | 2 / 0 | |
| 7.13.7 | 2 / 0 | |
| 7.13.6 | 2 / 0 | |
| 7.13.5 | 2 / 0 | |
| 7.13.4 | 2 / 0 | |
| 7.13.3 | 2 / 0 | |
| 7.13.2 | 2 / 0 | |
| 7.13.1 | 2 / 0 | |
| 7.13.0 | 2 / 0 | |
| 7.12.22 | 2 / 0 | |
| 7.12.21 | 2 / 0 | |
| 7.12.20 | 2 / 0 | |
| 7.12.19 | 2 / 0 | |
| 7.12.18 | 2 / 0 | |
| 7.12.17 | 2 / 0 | |
| 7.12.16 | 2 / 0 | |
| 7.12.15 | 2 / 0 | |
| 7.12.14 | 2 / 0 | |
| 7.12.13 | 2 / 0 | |
| 7.12.12 | 2 / 0 | |
| 7.12.11 | 2 / 0 | |
| 7.12.10 | 2 / 0 | |
| 7.12.9 | 2 / 0 | |
| 7.12.8 | 2 / 0 | |
| 7.12.7 | 2 / 0 | |
| 7.12.6 | 2 / 0 | |
| 7.12.5 | 2 / 0 | |
| 7.12.4 | 2 / 0 | |
| 7.12.3 | 2 / 0 | |
| 7.12.2 | 2 / 0 | |
| 7.12.1 | 2 / 0 | |
| 7.12.0 | 2 / 0 | |
| 7.11.0 | 2 / 0 | |
| 7.10.3 | 2 / 0 | |
| 7.10.2 | 2 / 0 | |
| 7.10.1 | 2 / 0 | |
| 7.10.0 | 2 / 0 | |
| 7.9.0 | 2 / 0 | |
| 7.8.0 | 2 / 0 | |
| 7.7.4 | 2 / 0 | |
| 7.7.3 | 2 / 0 | |
| 7.7.2 | 2 / 0 | |
| 7.7.1 | 2 / 0 | |
| 7.7.0 | 2 / 0 | |
| 7.6.7 | 2 / 0 | |
| 7.6.6 | 2 / 0 | |
| 7.6.5 | 2 / 0 | |
| 7.6.4 | 2 / 0 | |
| 7.6.3 | 2 / 0 | |
| 7.6.2 | 2 / 0 | |
| 7.6.1 | 2 / 0 | |
| 7.6.0 | 2 / 0 | |
| 7.5.1 | 2 / 0 | |
| 7.5.0 | 2 / 0 | |
| 7.4.9 | 2 / 0 | |
| 7.4.8 | 2 / 0 | |
| 7.4.7 | 2 / 0 | |
| 7.4.6 | 2 / 0 | |
| 7.4.5 | 2 / 0 | |
| 7.4.4 | 2 / 0 | |
| 7.4.3 | 2 / 0 | |
| 7.4.2 | 2 / 0 | |
| 7.4.1 | 2 / 0 | |
| 7.4.0 | 2 / 0 | |
| 7.3.1 | 2 / 0 | |
| 7.3.0 | 2 / 0 | |
| 7.2.2 | 2 / 0 | |
| 7.2.1 | 2 / 0 | |
| 7.2.0 | 2 / 0 | |
| 7.1.0 | 2 / 0 | |
| 7.0.17 | 2 / 0 | |
| 7.0.16 | 2 / 0 | |
| 7.0.15 | 2 / 0 | |
| 7.0.14 | 2 / 0 | |
| 7.0.13 | 2 / 0 | |
| 7.0.12 | 2 / 0 | |
| 7.0.11 | 2 / 0 | |
| 7.0.10 | 2 / 0 | |
| 7.0.9 | 2 / 0 | |
| 7.0.8 | 2 / 0 | |
| 7.0.7 | 2 / 0 | |
| 7.0.6 | 2 / 0 | |
| 7.0.5 | 2 / 0 | |
| 7.0.4 | 2 / 0 | |
| 7.0.3 | 2 / 0 | |
| 7.0.2 | 2 / 0 | |
| 7.0.1 | 2 / 0 | |
| 7.0.0 | 2 / 0 |
v7.13.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.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.