@electrum-cash/web-socket
@electrum-cash/web-socket implements the ElectrumSocket interface using web sockets.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a peer/transitive dep re-exported via @monsterbitar/isomorphic-ws; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): Type-only package loaded by TypeScript convention, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:async-mutex | AI (phantom-deps): Likely used in compiled output or re-exported; phantom-dep heuristic fires on TS build artifacts. | ai | |
| phantom-deps | phantom-dep:lossless-json | AI (phantom-deps): Same as async-mutex — TS build artifact pattern, stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.2.3 | 7 / 19 | |
| 1.2.2 | 7 / 19 | |
| 1.2.1 | 7 / 19 | |
| 1.2.0 | 7 / 19 | |
| 1.1.1 | 7 / 19 | |
| 1.0.3 | 7 / 18 | |
| 1.0.2 | 7 / 18 | |
| 1.0.1 | 7 / 18 |
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
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.