@frontegg/react-hooks
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@frontegg/redux-store | AI (dependencies): Internal Frontegg monorepo dependency; stable pattern across all versions of this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped sub-package of established Frontegg SDK; missing metadata is a pattern across all their packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with Frontegg's sub-package publishing pattern across 1237 versions. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only dev dependency; not imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/react-is | AI (phantom-deps): Type-only dev dependency; not imported at runtime by convention. | ai |
Versions (showing 19 of 119)
| Version | Deps | Published |
|---|---|---|
| 7.19.0 | 8 / 0 | |
| 7.18.0 | 8 / 0 | |
| 7.17.0 | 8 / 0 | |
| 7.16.0 | 8 / 0 | |
| 7.15.0 | 8 / 0 | |
| 7.14.0 | 8 / 0 | |
| 7.13.0 | 8 / 0 | |
| 7.12.0 | 8 / 0 | |
| 7.11.0 | 8 / 0 | |
| 7.10.0 | 8 / 0 | |
| 7.9.0 | 8 / 0 | |
| 7.8.0 | 8 / 0 | |
| 7.7.0 | 8 / 0 | |
| 7.6.0 | 8 / 0 | |
| 7.5.0 | 8 / 0 | |
| 7.4.0 | 8 / 0 | |
| 7.3.0 | 7 / 0 | |
| 7.2.0 | 7 / 0 | |
| 7.1.0 | 5 / 0 |
v7.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.