@supabase/supabase-js
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo migration dropped gitHead; SLSA attestation provides stronger integrity signal. | ai | |
| dependencies | unvetted-dep:@supabase/node-fetch | AI (dependencies): @supabase/node-fetch is Supabase's own maintained fork of node-fetch, an intentional and stable dependency used across the Supabase ecosystem. Not a risk for this package. | ai | |
| dependencies | unvetted-dep:@supabase/realtime-js | AI (dependencies): First-party Supabase monorepo sub-package, always released in lockstep with supabase-js. Not a third-party unvetted dependency. | ai | |
| dependencies | unvetted-dep:@supabase/auth-js | AI (dependencies): First-party Supabase monorepo sub-package, always released in lockstep with supabase-js. Not a third-party unvetted dependency. | ai | |
| dependencies | unvetted-dep:@supabase/postgrest-js | AI (dependencies): First-party Supabase monorepo sub-package, always released in lockstep with supabase-js. Not a third-party unvetted dependency. | ai | |
| dependencies | unvetted-dep:@supabase/functions-js | AI (dependencies): First-party Supabase monorepo sub-package, always released in lockstep with supabase-js. Not a third-party unvetted dependency. | ai | |
| dependencies | unvetted-dep:@supabase/storage-js | AI (dependencies): First-party Supabase monorepo sub-package, always released in lockstep with supabase-js. Not a third-party unvetted dependency. | ai |
Versions (showing 100 of 238)
| Version | Deps | Published |
|---|---|---|
| 2.50.2 | 6 / 20 | |
| 2.50.1 | 6 / 20 | |
| 2.50.0 | 6 / 20 | |
| 2.49.10 | 6 / 19 | |
| 2.49.9 | 6 / 19 | |
| 2.49.8 | 6 / 18 | |
| 2.49.7 | 6 / 18 | |
| 2.49.6 | 6 / 18 | |
| 2.49.5 | 6 / 18 | |
| 2.49.4 | 6 / 18 | |
| 2.49.3 | 6 / 18 | |
| 2.49.2 | 6 / 18 | |
| 2.49.1 | 6 / 18 | |
| 2.49.0 | 6 / 18 | |
| 2.48.1 | 6 / 18 | |
| 2.48.0 | 6 / 18 | |
| 2.47.16 | 6 / 18 | |
| 2.47.15 | 6 / 18 | |
| 2.47.14 | 6 / 18 | |
| 2.47.13 | 6 / 18 | |
| 2.47.12 | 6 / 18 | |
| 2.47.11 | 6 / 18 | |
| 2.47.10 | 6 / 18 | |
| 2.47.9 | 6 / 18 | |
| 2.47.8 | 6 / 18 | |
| 2.47.7 | 6 / 18 | |
| 2.47.6 | 6 / 18 | |
| 2.47.5 | 6 / 18 | |
| 2.47.4 | 6 / 18 | |
| 2.47.3 | 6 / 18 | |
| 2.47.2 | 6 / 18 | |
| 2.47.1 | 6 / 18 | |
| 2.47.0 | 6 / 18 | |
| 2.46.2 | 6 / 18 | |
| 2.46.1 | 6 / 18 | |
| 2.46.0 | 6 / 18 | |
| 2.45.6 | 6 / 18 | |
| 2.45.5 | 6 / 18 | |
| 2.45.4 | 6 / 18 | |
| 2.45.3 | 6 / 18 | |
| 2.45.2 | 6 / 18 | |
| 2.45.1 | 6 / 18 | |
| 2.45.0 | 6 / 18 | |
| 2.44.4 | 6 / 18 | |
| 2.44.3 | 6 / 18 | |
| 2.44.2 | 6 / 18 | |
| 2.44.1 | 6 / 18 | |
| 2.44.0 | 6 / 18 | |
| 2.43.6 | 6 / 18 | |
| 2.43.5 | 6 / 18 | |
| 2.43.4 | 6 / 19 | |
| 2.43.3 | 6 / 20 | |
| 2.43.2 | 6 / 19 | |
| 2.43.1 | 6 / 17 | |
| 2.43.0 | 6 / 17 | |
| 2.42.7 | 6 / 17 | |
| 2.42.6 | 6 / 17 | |
| 2.42.5 | 6 / 17 | |
| 2.42.4 | 6 / 17 | |
| 2.42.3 | 6 / 17 | |
| 2.42.2 | 6 / 17 | |
| 2.42.1 | 6 / 17 | |
| 2.42.0 | 6 / 17 | |
| 2.41.1 | 6 / 17 | |
| 2.41.0 | 6 / 17 | |
| 2.40.0 | 6 / 17 | |
| 2.39.8 | 6 / 17 | |
| 2.39.7 | 6 / 17 | |
| 2.39.6 | 6 / 16 | |
| 2.39.5 | 6 / 16 | |
| 2.39.4 | 6 / 16 | |
| 2.39.3 | 6 / 15 | |
| 2.39.2 | 6 / 15 | |
| 2.39.1 | 6 / 15 | |
| 2.39.0 | 6 / 15 | |
| 2.38.5 | 6 / 15 | |
| 2.38.4 | 6 / 15 | |
| 2.38.3 | 6 / 15 | |
| 2.38.2 | 6 / 15 | |
| 2.38.1 | 6 / 15 | |
| 2.38.0 | 6 / 15 | |
| 2.37.0 | 6 / 15 | |
| 2.36.0 | 6 / 15 | |
| 2.35.0 | 6 / 15 | |
| 2.34.0 | 6 / 15 | |
| 2.33.2 | 6 / 15 | |
| 2.33.1 | 6 / 15 | |
| 2.33.0 | 6 / 15 | |
| 2.32.0 | 6 / 15 | |
| 2.31.0 | 6 / 15 | |
| 2.30.0 | 6 / 15 | |
| 2.29.0 | 6 / 15 | |
| 2.28.0 | 6 / 15 | |
| 2.27.0 | 6 / 15 | |
| 2.26.0 | 6 / 15 | |
| 2.25.0 | 6 / 15 | |
| 2.24.0 | 6 / 15 | |
| 2.23.0 | 6 / 15 | |
| 2.22.0 | 6 / 15 | |
| 2.21.0 | 6 / 15 |
v2.49.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.46.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.