@crossmint/client-sdk-auth
This SDK provides a set of tools for authenticating users in a Crossmint-powered application on the client-side. It simplifies the process of handling authentication tokens, managing user sessions, and integrating various authentication methods into your
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@farcaster/auth-kit | AI (dependencies): @farcaster/auth-kit is a legitimate Farcaster auth library; stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Crossmint SDK org; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 51 of 69)
| Version | Deps | Published |
|---|---|---|
| 1.3.16 | 4 / 0 | |
| 1.3.15 | 4 / 0 | |
| 1.3.14 | 4 / 0 | |
| 1.3.13 | 4 / 0 | |
| 1.3.12 | 4 / 0 | |
| 1.3.11 | 4 / 0 | |
| 1.3.10 | 4 / 0 | |
| 1.3.9 | 4 / 0 | |
| 1.3.8 | 4 / 0 | |
| 1.3.7 | 4 / 0 | |
| 1.3.6 | 4 / 0 | |
| 1.3.5 | 4 / 0 | |
| 1.3.4 | 4 / 0 | |
| 1.3.3 | 4 / 0 | |
| 1.3.2 | 4 / 0 | |
| 1.3.1 | 4 / 0 | |
| 1.3.0 | 4 / 0 | |
| 1.2.51 | 5 / 0 | |
| 1.2.47 | 5 / 0 | |
| 1.2.40 | 5 / 0 | |
| 1.2.37 | 5 / 0 | |
| 1.2.36 | 5 / 0 | |
| 1.2.35 | 5 / 0 | |
| 1.2.32 | 5 / 0 | |
| 1.2.31 | 5 / 0 | |
| 1.2.30 | 5 / 0 | |
| 1.2.29 | 5 / 0 | |
| 1.2.27 | 5 / 0 | |
| 1.2.25 | 5 / 0 | |
| 1.2.22 | 5 / 0 | |
| 1.2.21 | 5 / 0 | |
| 1.2.15 | 5 / 0 | |
| 1.2.14 | 5 / 0 | |
| 1.2.13 | 5 / 0 | |
| 1.2.11 | 5 / 0 | |
| 1.2.7 | 5 / 0 | |
| 1.2.5 | 5 / 0 | |
| 1.2.3 | 5 / 0 | |
| 1.2.2 | 5 / 0 | |
| 1.2.1 | 5 / 0 | |
| 1.2.0 | 5 / 0 | |
| 1.1.26 | 5 / 0 | |
| 1.1.25 | 5 / 0 | |
| 1.1.24 | 5 / 0 | |
| 1.1.23 | 5 / 0 | |
| 1.1.22 | 5 / 0 | |
| 1.1.21 | 5 / 0 | |
| 1.1.20 | 5 / 0 | |
| 1.1.19 | 5 / 0 | |
| 1.1.18 | 5 / 0 | |
| 1.1.17 | 5 / 0 |
v1.3.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.