@well-played.gg/react-sdk
This is the official [WellPlayed](https://well-played.gg) React SDK. It provides a set of components and hooks to help you integrate WellPlayed into your React application and interact with the WellPlayed API.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@tiptap/react | AI (phantom-deps): Listed as runtime dependency; phantom-dep heuristic fires on config-only references, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/starter-kit | AI (phantom-deps): Listed as runtime dependency; phantom-dep heuristic fires on config-only references, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-link | AI (phantom-deps): Listed as runtime dependency; phantom-dep heuristic fires on config-only references, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-highlight | AI (phantom-deps): Listed as runtime dependency; phantom-dep heuristic fires on config-only references, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-subscript | AI (phantom-deps): Listed as runtime dependency; phantom-dep heuristic fires on config-only references, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-underline | AI (phantom-deps): Listed as runtime dependency; phantom-dep heuristic fires on config-only references, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-text-align | AI (phantom-deps): Listed as runtime dependency; phantom-dep heuristic fires on config-only references, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-superscript | AI (phantom-deps): Listed as runtime dependency; phantom-dep heuristic fires on config-only references, stable false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.2.4 | 10 / 9 | |
| 2.2.3 | 10 / 9 | |
| 2.2.2 | 10 / 9 | |
| 2.2.1 | 10 / 9 | |
| 2.2.0 | 10 / 8 | |
| 2.1.4 | 10 / 8 | |
| 2.1.3 | 10 / 8 | |
| 2.1.2 | 10 / 8 | |
| 2.1.1 | 10 / 8 | |
| 2.1.0 | 10 / 8 | |
| 2.0.7 | 10 / 8 | |
| 2.0.6 | 10 / 8 | |
| 2.0.5 | 10 / 8 | |
| 2.0.4 | 10 / 8 | |
| 2.0.3 | 10 / 8 | |
| 2.0.2 | 10 / 8 |
v2.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.