@supabase/gotrue-js
Official SDK for Supabase Auth
Supply chain provenance
Status for the latest visible version.
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Standard JWT/base64url decode helper, not malicious payload hiding. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used in a Proxy trap for symbol inspection; legitimate pattern in this SDK. | ai |
Versions (showing 100 of 198)
| Version | Deps | Published |
|---|---|---|
| 2.108.2 | 1 / 12 | |
| 2.108.1 | 1 / 12 | |
| 2.108.0 | 1 / 12 | |
| 2.107.0 | 1 / 12 | |
| 2.105.4 | 1 / 1 | |
| 2.105.3 | 1 / 1 | |
| 2.105.2 | 1 / 1 | |
| 2.105.1 | 1 / 1 | |
| 2.105.0 | 1 / 1 | |
| 2.104.1 | 1 / 1 | |
| 2.104.0 | 1 / 1 | |
| 2.103.3 | 1 / 1 | |
| 2.103.2 | 1 / 1 | |
| 2.103.1 | 1 / 1 | |
| 2.103.0 | 1 / 1 | |
| 2.102.1 | 1 / 1 | |
| 2.102.0 | 1 / 1 | |
| 2.101.1 | 1 / 1 | |
| 2.101.0 | 1 / 1 | |
| 2.100.1 | 1 / 1 | |
| 2.100.0 | 1 / 1 | |
| 2.99.3 | 1 / 1 | |
| 2.99.2 | 1 / 1 | |
| 2.99.1 | 1 / 1 | |
| 2.99.0 | 1 / 1 | |
| 2.98.0 | 1 / 1 | |
| 2.97.0 | 1 / 1 | |
| 2.96.0 | 1 / 1 | |
| 2.95.3 | 1 / 1 | |
| 2.95.2 | 1 / 1 | |
| 2.95.1 | 1 / 1 | |
| 2.95.0 | 1 / 1 | |
| 2.94.1 | 1 / 1 | |
| 2.94.0 | 1 / 1 | |
| 2.93.3 | 1 / 1 | |
| 2.93.2 | 1 / 1 | |
| 2.93.1 | 1 / 1 | |
| 2.93.0 | 1 / 1 | |
| 2.92.0 | 1 / 1 | |
| 2.91.2 | 1 / 1 | |
| 2.91.1 | 1 / 1 | |
| 2.91.0 | 1 / 1 | |
| 2.90.1 | 1 / 1 | |
| 2.90.0 | 1 / 1 | |
| 2.89.0 | 1 / 1 | |
| 2.88.0 | 1 / 1 | |
| 2.87.3 | 1 / 1 | |
| 2.87.2 | 1 / 1 | |
| 2.87.1 | 1 / 1 | |
| 2.87.0 | 1 / 1 | |
| 2.86.2 | 1 / 1 | |
| 2.86.1 | 1 / 1 | |
| 2.86.0 | 1 / 1 | |
| 2.85.0 | 1 / 1 | |
| 2.84.0 | 1 / 1 | |
| 2.83.0 | 1 / 1 | |
| 2.82.0 | 1 / 1 | |
| 2.81.1 | 1 / 1 | |
| 2.81.0 | 1 / 1 | |
| 2.80.0 | 1 / 1 | |
| 2.79.0 | 1 / 1 | |
| 2.78.0 | 2 / 1 | |
| 2.77.0 | 2 / 2 | |
| 2.76.1 | 2 / 2 | |
| 2.76.0 | 1 / 2 | |
| 2.75.1 | 1 / 2 | |
| 2.75.0 | 1 / 2 | |
| 2.74.0 | 1 / 2 | |
| 2.72.0 | 1 / 25 | |
| 2.71.1 | 1 / 25 | |
| 2.71.0 | 1 / 25 | |
| 2.70.0 | 1 / 26 | |
| 2.69.1 | 1 / 25 | |
| 2.69.0 | 1 / 25 | |
| 2.68.0 | 1 / 25 | |
| 2.67.3 | 1 / 25 | |
| 2.67.2 | 1 / 25 | |
| 2.67.1 | 1 / 25 | |
| 2.67.0 | 1 / 25 | |
| 2.66.1 | 1 / 25 | |
| 2.66.0 | 1 / 25 | |
| 2.65.1 | 1 / 25 | |
| 2.65.0 | 1 / 25 | |
| 2.64.4 | 1 / 25 | |
| 2.64.3 | 1 / 25 | |
| 2.64.2 | 1 / 25 | |
| 2.64.1 | 1 / 25 | |
| 2.64.0 | 1 / 25 | |
| 2.63.2 | 1 / 25 | |
| 2.63.1 | 1 / 25 | |
| 2.63.0 | 1 / 25 | |
| 2.62.2 | 1 / 25 | |
| 2.62.1 | 1 / 25 | |
| 2.62.0 | 1 / 25 | |
| 2.61.0 | 1 / 25 | |
| 2.60.1 | 1 / 25 | |
| 2.60.0 | 1 / 25 | |
| 2.59.0 | 1 / 25 | |
| 2.58.0 | 1 / 25 | |
| 2.57.1 | 1 / 25 |
v2.69.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.69.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.68.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.67.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.66.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.65.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.64.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.64.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.64.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.64.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.63.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.57.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.