@gamepark/react-client
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@trpc/server | AI (phantom-deps): Declared as runtime dep for type re-exports; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash.shuffle | AI (phantom-deps): Likely used indirectly or re-exported; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:intl-messageformat | AI (phantom-deps): Likely used indirectly or re-exported; stable false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 7.6.6 | 10 / 14 | |
| 7.6.5 | 10 / 14 | |
| 7.6.4 | 10 / 14 | |
| 7.6.3 | 10 / 14 | |
| 7.6.2 | 10 / 14 | |
| 7.6.1 | 10 / 14 | |
| 7.6.0 | 10 / 14 | |
| 7.5.7 | 10 / 14 | |
| 7.5.6 | 10 / 14 | |
| 7.5.5 | 10 / 14 | |
| 7.5.4 | 10 / 14 | |
| 7.5.3 | 10 / 14 | |
| 7.5.2 | 10 / 14 | |
| 7.5.1 | 10 / 14 | |
| 7.5.0 | 10 / 14 | |
| 7.4.1 | 10 / 14 | |
| 7.4.0 | 10 / 14 | |
| 7.3.2 | 10 / 14 | |
| 7.3.1 | 9 / 15 | |
| 7.3.0 | 9 / 15 | |
| 7.2.0 | 5 / 15 | |
| 5.25.1 | 24 / 13 | |
| 5.25.0 | 24 / 13 | |
| 5.24.0 | 23 / 13 |
v7.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v5.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.