@frontegg/react-core
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:process | AI (phantom-deps): Declared as dependency for browser polyfill; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:rc-util | AI (phantom-deps): Declared dependency used transitively via rc-dialog; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Common UI utility declared as dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.0.23 | 16 / 0 | |
| 4.0.22 | 16 / 0 | |
| 4.0.21 | 16 / 0 | |
| 4.0.20 | 16 / 0 | |
| 4.0.19 | 16 / 0 | |
| 4.0.18 | 16 / 0 | |
| 4.0.17 | 16 / 0 | |
| 4.0.16 | 16 / 0 | |
| 4.0.15 | 16 / 0 | |
| 4.0.14 | 16 / 0 | |
| 4.0.13 | 15 / 0 | |
| 4.0.12 | 14 / 0 | |
| 4.0.11 | 14 / 0 | |
| 4.0.10 | 14 / 0 | |
| 4.0.9 | 14 / 0 | |
| 4.0.8 | 14 / 0 | |
| 4.0.7 | 14 / 0 | |
| 4.0.6 | 14 / 0 | |
| 4.0.5 | 14 / 0 | |
| 4.0.4 | 14 / 0 | |
| 4.0.3 | 14 / 0 | |
| 4.0.2 | 14 / 0 | |
| 4.0.1 | 14 / 0 |
v4.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.