hyperswarm-proxy-ws
Proxy hyperswarm connections over websockets with auto-reconnect logic
hyperswarm-proxy-ws@1.2.0 was published on 2020-09-03. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All hyperswarm-proxy-ws versions · Permanent reference to 1.2.0
Package specifications
| Version | 1.2.0 |
|---|---|
| License declaration | MIT |
| Published | 2020-09-03T20:05:50.457Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 7.45 KiB |
| Published file count | 6 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 64 |
| Repository stars | 14 |
| Repository forks | 7 |
Install hyperswarm-proxy-ws 1.2.0
npm install hyperswarm-proxy-ws@1.2.0 pnpm add hyperswarm-proxy-ws@1.2.0 yarn add hyperswarm-proxy-ws@1.2.0
Runtime dependencies
- hyperswarm-proxy ^1.4.0
- websocket-stream ^5.5.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- hyperswarm-proxy@1.5.2 — direct
- websocket-stream@5.5.2 — direct
- @hyperswarm/network@2.1.0 — indirect
- length-prefixed-stream@2.0.0 — indirect
- pump@3.0.4 — indirect
- duplexify@3.7.1 — indirect
- inherits@2.0.4 — indirect
- readable-stream@2.3.8 — indirect
- safe-buffer@5.2.1 — indirect
- ws@3.3.3 — indirect
- xtend@4.0.2 — indirect
- @hyperswarm/discovery@2.0.1 — indirect
- nanoresource@1.3.0 — indirect
- utp-native@2.5.3 — indirect
- readable-stream@3.6.2 — indirect
- varint@5.0.0 — indirect
- end-of-stream@1.4.5 — indirect
- once@1.4.0 — indirect
- readable-stream@2.3.8 — indirect
- stream-shift@1.0.3 — indirect
- core-util-is@1.0.3 — indirect
- isarray@1.0.0 — indirect
- process-nextick-args@2.0.1 — indirect
- safe-buffer@5.1.2 — indirect
- string_decoder@1.1.1 — indirect
- util-deprecate@1.0.2 — indirect
- async-limiter@1.0.1 — indirect
- safe-buffer@5.1.2 — indirect
- ultron@1.1.1 — indirect
- @hyperswarm/dht@4.0.1 — indirect
- multicast-dns@7.2.5 — indirect
- timeout-refresh@1.0.3 — indirect
- napi-macros@2.2.2 — indirect
- node-gyp-build@4.8.4 — indirect
- unordered-set@2.0.1 — indirect
- string_decoder@1.3.0 — indirect
- wrappy@1.0.2 — indirect
- safe-buffer@5.1.2 — indirect
- string_decoder@1.1.1 — indirect
- safe-buffer@5.1.2 — indirect
- @hyperswarm/hypersign@2.1.1 — indirect
- dht-rpc@4.9.6 — indirect
- guard-timeout@2.0.0 — indirect
- hashlru@2.3.0 — indirect
- protocol-buffers-encodings@1.2.0 — indirect
- record-cache@1.2.0 — indirect
- sodium-native@3.4.1 — indirect
- dns-packet@5.6.1 — indirect
- thunky@1.1.0 — indirect
- blake2b-universal@1.0.1 — indirect
- codecs@2.2.0 — indirect
- ipv4-peers@2.0.0 — indirect
- k-bucket@5.1.0 — indirect
- speedometer@1.1.0 — indirect
- stream-collector@1.0.1 — indirect
- time-ordered-set@1.0.2 — indirect
- xor-distance@2.0.0 — indirect
- b4a@1.9.0 — indirect
- signed-varint@2.0.1 — indirect
- @leichtgewicht/ip-codec@2.0.5 — indirect
- blake2b@2.1.4 — indirect
- randombytes@2.1.0 — indirect
- blake2b-wasm@2.4.0 — indirect
- nanoassert@2.0.0 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 1/10 — Found 2/12 approved changesets -- score normalized to 1 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | 0/10 — security policy file not detected |
Evidence and freshness
- https://registry.npmjs.org/hyperswarm-proxy-ws/1.2.0 — retrieved 2026-10-29T15:26:01.775Z
- https://api.deps.dev/v3/systems/npm/packages/hyperswarm-proxy-ws/versions/1.2.0 — retrieved 2026-10-29T15:26:02.300Z
- https://api.deps.dev/v3/systems/npm/packages/hyperswarm-proxy-ws/versions/1.2.0:dependencies — retrieved 2026-10-29T15:26:02.297Z
- https://api.deps.dev/v3/projects/github.com%2FRangerMauve%2Fhyperswarm-proxy-ws — retrieved 2026-10-29T15:26:02.464Z