@crossmint/server-sdk
This SDK provides a set of tools for authenticating users in a Crossmint-powered application using server-side rendering (SSR). It simplifies the process of handling authentication tokens and managing user sessions, making it easier to integrate authentic
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions is confirmed by SLSA provenance attestation; legitimate CI/CD migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD-attested publish; no malicious indicators present. | ai |
Versions (showing 92 of 92)
| Version | Deps | Published |
|---|---|---|
| 1.2.78 | 3 / 3 | |
| 1.2.77 | 3 / 3 | |
| 1.2.76 | 3 / 0 | |
| 1.2.75 | 3 / 0 | |
| 1.2.74 | 3 / 0 | |
| 1.2.73 | 3 / 0 | |
| 1.2.72 | 3 / 0 | |
| 1.2.71 | 3 / 0 | |
| 1.2.70 | 3 / 0 | |
| 1.2.69 | 3 / 0 | |
| 1.2.68 | 3 / 0 | |
| 1.2.67 | 3 / 0 | |
| 1.2.66 | 3 / 0 | |
| 1.2.65 | 3 / 0 | |
| 1.2.64 | 3 / 0 | |
| 1.2.63 | 3 / 0 | |
| 1.2.62 | 3 / 0 | |
| 1.2.61 | 3 / 0 | |
| 1.2.60 | 3 / 0 | |
| 1.2.59 | 3 / 0 | |
| 1.2.58 | 3 / 0 | |
| 1.2.57 | 3 / 0 | |
| 1.2.56 | 3 / 0 | |
| 1.2.55 | 3 / 0 | |
| 1.2.54 | 3 / 0 | |
| 1.2.53 | 3 / 0 | |
| 1.2.52 | 3 / 0 | |
| 1.2.51 | 3 / 0 | |
| 1.2.49 | 3 / 0 | |
| 1.2.48 | 3 / 0 | |
| 1.2.47 | 3 / 0 | |
| 1.2.46 | 3 / 0 | |
| 1.2.45 | 3 / 0 | |
| 1.2.44 | 3 / 0 | |
| 1.2.43 | 3 / 0 | |
| 1.2.42 | 3 / 0 | |
| 1.2.41 | 3 / 0 | |
| 1.2.40 | 3 / 0 | |
| 1.2.39 | 3 / 0 | |
| 1.2.38 | 3 / 0 | |
| 1.2.37 | 3 / 0 | |
| 1.2.36 | 3 / 0 | |
| 1.2.35 | 3 / 0 | |
| 1.2.34 | 3 / 0 | |
| 1.2.33 | 3 / 0 | |
| 1.2.32 | 3 / 0 | |
| 1.2.31 | 3 / 0 | |
| 1.2.30 | 3 / 0 | |
| 1.2.29 | 3 / 0 | |
| 1.2.28 | 3 / 0 | |
| 1.2.27 | 3 / 0 | |
| 1.2.26 | 3 / 0 | |
| 1.2.25 | 3 / 0 | |
| 1.2.24 | 3 / 0 | |
| 1.2.23 | 3 / 0 | |
| 1.2.22 | 3 / 0 | |
| 1.2.21 | 3 / 0 | |
| 1.2.20 | 3 / 0 | |
| 1.2.19 | 3 / 0 | |
| 1.2.18 | 3 / 0 | |
| 1.2.17 | 3 / 0 | |
| 1.2.16 | 3 / 0 | |
| 1.2.15 | 3 / 0 | |
| 1.2.14 | 3 / 0 | |
| 1.2.13 | 3 / 0 | |
| 1.2.12 | 3 / 0 | |
| 1.2.11 | 3 / 0 | |
| 1.2.10 | 3 / 0 | |
| 1.2.9 | 3 / 0 | |
| 1.2.8 | 3 / 0 | |
| 1.2.7 | 3 / 0 | |
| 1.2.6 | 3 / 0 | |
| 1.2.5 | 3 / 0 | |
| 1.2.4 | 3 / 0 | |
| 1.2.3 | 3 / 0 | |
| 1.2.2 | 3 / 0 | |
| 1.2.1 | 3 / 0 | |
| 1.2.0 | 3 / 0 | |
| 1.1.10 | 4 / 1 | |
| 1.1.9 | 4 / 1 | |
| 1.1.8 | 4 / 1 | |
| 1.1.7 | 4 / 1 | |
| 1.1.6 | 4 / 1 | |
| 1.1.5 | 4 / 1 | |
| 1.1.4 | 4 / 1 | |
| 1.1.3 | 4 / 1 | |
| 1.1.2 | 4 / 1 | |
| 1.1.1 | 4 / 1 | |
| 1.1.0 | 4 / 1 | |
| 1.0.2 | 4 / 1 | |
| 1.0.1 | 4 / 1 | |
| 1.0.0 | 4 / 1 |
v1.2.78
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.77
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.76
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.75
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.