@live-change/dao-websocket
live-change dao websocket transport
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:bufferutil | AI (phantom-deps): Optional ws peer dep; declared for perf but not directly imported — stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:utf-8-validate | AI (phantom-deps): Optional ws peer dep; same pattern as bufferutil. | ai | |
| phantom-deps | phantom-dep:supports-color | AI (phantom-deps): Transitive debug dep; commonly declared without direct import. | ai |
Versions (showing 100 of 340)
| Version | Deps | Published |
|---|---|---|
| 0.9.110 | 7 / 1 | |
| 0.9.109 | 7 / 1 | |
| 0.9.108 | 7 / 1 | |
| 0.9.107 | 7 / 1 | |
| 0.9.106 | 7 / 1 | |
| 0.9.105 | 7 / 1 | |
| 0.9.104 | 7 / 1 | |
| 0.9.103 | 7 / 1 | |
| 0.9.102 | 7 / 1 | |
| 0.9.101 | 7 / 1 | |
| 0.9.100 | 7 / 1 | |
| 0.9.99 | 7 / 1 | |
| 0.9.98 | 7 / 1 | |
| 0.9.97 | 7 / 1 | |
| 0.9.96 | 7 / 1 | |
| 0.9.95 | 7 / 1 | |
| 0.9.94 | 7 / 1 | |
| 0.9.93 | 7 / 1 | |
| 0.9.92 | 7 / 1 | |
| 0.9.91 | 7 / 1 | |
| 0.9.90 | 7 / 1 | |
| 0.9.89 | 7 / 1 | |
| 0.9.88 | 7 / 1 | |
| 0.9.87 | 7 / 1 | |
| 0.9.86 | 7 / 1 | |
| 0.9.85 | 7 / 1 | |
| 0.9.84 | 7 / 1 | |
| 0.9.83 | 7 / 1 | |
| 0.9.82 | 7 / 1 | |
| 0.9.81 | 7 / 1 | |
| 0.9.80 | 7 / 1 | |
| 0.9.79 | 7 / 1 | |
| 0.9.78 | 7 / 1 | |
| 0.9.77 | 7 / 1 | |
| 0.9.76 | 7 / 1 | |
| 0.9.75 | 7 / 1 | |
| 0.9.74 | 7 / 1 | |
| 0.9.73 | 7 / 1 | |
| 0.9.72 | 7 / 1 | |
| 0.9.71 | 7 / 1 | |
| 0.9.70 | 7 / 1 | |
| 0.9.69 | 7 / 1 | |
| 0.9.68 | 7 / 1 | |
| 0.9.67 | 7 / 1 | |
| 0.9.66 | 7 / 1 | |
| 0.9.65 | 7 / 1 | |
| 0.9.64 | 7 / 1 | |
| 0.9.63 | 7 / 1 | |
| 0.9.62 | 7 / 1 | |
| 0.9.61 | 7 / 1 | |
| 0.9.60 | 7 / 1 | |
| 0.9.59 | 7 / 1 | |
| 0.9.58 | 7 / 1 | |
| 0.9.57 | 7 / 1 | |
| 0.9.56 | 7 / 1 | |
| 0.9.55 | 7 / 1 | |
| 0.9.54 | 7 / 1 | |
| 0.9.53 | 7 / 1 | |
| 0.9.52 | 7 / 1 | |
| 0.9.51 | 7 / 1 | |
| 0.9.50 | 7 / 1 | |
| 0.9.49 | 7 / 1 | |
| 0.9.48 | 7 / 1 | |
| 0.9.47 | 7 / 1 | |
| 0.9.46 | 7 / 1 | |
| 0.9.45 | 7 / 1 | |
| 0.9.44 | 7 / 1 | |
| 0.9.43 | 7 / 1 | |
| 0.9.42 | 7 / 1 | |
| 0.9.41 | 7 / 1 | |
| 0.9.40 | 7 / 1 | |
| 0.9.39 | 7 / 1 | |
| 0.9.38 | 7 / 1 | |
| 0.9.37 | 7 / 1 | |
| 0.9.36 | 7 / 1 | |
| 0.9.35 | 7 / 1 | |
| 0.9.34 | 7 / 1 | |
| 0.9.33 | 7 / 1 | |
| 0.9.32 | 7 / 1 | |
| 0.9.31 | 7 / 1 | |
| 0.9.30 | 7 / 1 | |
| 0.9.29 | 7 / 1 | |
| 0.9.28 | 7 / 1 | |
| 0.9.27 | 7 / 1 | |
| 0.9.26 | 7 / 1 | |
| 0.9.25 | 7 / 1 | |
| 0.9.24 | 7 / 1 | |
| 0.9.23 | 7 / 1 | |
| 0.9.22 | 7 / 1 | |
| 0.9.21 | 7 / 1 | |
| 0.9.20 | 7 / 1 | |
| 0.9.19 | 7 / 1 | |
| 0.9.18 | 7 / 1 | |
| 0.9.17 | 7 / 1 | |
| 0.9.16 | 7 / 1 | |
| 0.9.15 | 7 / 1 | |
| 0.9.14 | 7 / 1 | |
| 0.9.13 | 7 / 1 | |
| 0.9.12 | 7 / 1 | |
| 0.9.11 | 7 / 1 |
v0.9.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.