@supabase/realtime-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 | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Controlled WebSocket module loader pattern; moduleId is not user-supplied, stable across versions. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a runtime peer dep used via dynamic require in the WebSocket factory; not a phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@types/phoenix | AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): @types/ws is intentionally listed as a runtime dep to ship TypeScript types alongside the ws package; this is a packaging style choice, not a security issue. | ai |
Versions (showing 44 of 144)
| Version | Deps | Published |
|---|---|---|
| 2.11.9 | 4 / 18 | |
| 2.11.8 | 4 / 18 | |
| 2.11.7 | 4 / 18 | |
| 2.11.6 | 4 / 18 | |
| 2.11.5 | 4 / 18 | |
| 2.11.4 | 4 / 18 | |
| 2.11.3 | 4 / 18 | |
| 2.11.2 | 4 / 18 | |
| 2.11.1 | 4 / 18 | |
| 2.11.0 | 4 / 18 | |
| 2.10.9 | 4 / 18 | |
| 2.10.8 | 4 / 18 | |
| 2.10.7 | 4 / 17 | |
| 2.10.6 | 4 / 16 | |
| 2.10.5 | 4 / 14 | |
| 2.10.4 | 4 / 13 | |
| 2.10.3 | 4 / 13 | |
| 2.10.2 | 4 / 13 | |
| 2.10.1 | 4 / 13 | |
| 2.10.0 | 4 / 13 | |
| 2.9.5 | 4 / 13 | |
| 2.9.4 | 4 / 16 | |
| 2.9.3 | 4 / 16 | |
| 2.9.2 | 3 / 17 | |
| 2.9.1 | 3 / 17 | |
| 2.9.0 | 4 / 17 | |
| 2.8.4 | 4 / 16 | |
| 2.8.3 | 4 / 16 | |
| 2.8.2 | 4 / 16 | |
| 2.8.1 | 4 / 16 | |
| 2.8.0 | 4 / 16 | |
| 2.7.4 | 3 / 16 | |
| 2.7.3 | 3 / 16 | |
| 2.7.2 | 3 / 16 | |
| 2.7.1 | 3 / 16 | |
| 2.7.0 | 2 / 17 | |
| 2.6.0 | 2 / 17 | |
| 2.5.0 | 2 / 17 | |
| 2.4.0 | 2 / 17 | |
| 2.3.1 | 2 / 17 | |
| 2.3.0 | 2 / 17 | |
| 2.2.0 | 2 / 17 | |
| 2.1.0 | 2 / 17 | |
| 2.0.0 | 2 / 17 |
v2.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.