@gamepark/react-components
React components to ease board games adaptations
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:supports-webp | AI (dependencies): Small, popular webp-detection lib consistent with a React UI component library. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Single benign dependency addition, no install-script risk. | ai | |
| provenance | no-provenance | AI (provenance): Established gamepark org package; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Declared as a runtime dependency and used transitively via @fortawesome/react-fontawesome; stable false positive for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 5.25.0 | 5 / 7 | |
| 5.24.0 | 5 / 7 | |
| 5.21.0 | 5 / 7 | |
| 5.12.0 | 5 / 7 | |
| 5.11.0 | 5 / 7 | |
| 5.9.0 | 5 / 7 | |
| 5.8.11 | 5 / 7 | |
| 5.8.6 | 5 / 7 | |
| 5.8.5 | 5 / 7 | |
| 5.8.4 | 5 / 7 | |
| 5.8.2 | 5 / 7 | |
| 5.6.3 | 5 / 7 | |
| 5.5.4 | 5 / 7 | |
| 5.5.3 | 5 / 7 | |
| 5.5.2 | 5 / 7 | |
| 5.5.1 | 5 / 7 | |
| 5.5.0 | 5 / 7 | |
| 5.4.0 | 4 / 7 | |
| 5.3.0 | 4 / 7 | |
| 5.2.0 | 4 / 7 | |
| 5.0.0 | 4 / 7 |
v5.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.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.
v5.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.