hashring 0.0.7
A pure JavaScript hash ring based on libketama
hashring@0.0.7 was published on 2013-01-11. 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 hashring versions · Permanent reference to 0.0.7 · View npm registry JSON · Latest release
Package specifications
| Version | 0.0.7 |
|---|---|
| License declaration | Not declared |
| Published | 2013-01-11T16:03:52.440Z |
| 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 | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./lib/hashring.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 358 |
| Repository forks | 57 |
Install hashring 0.0.7
npm install hashring@0.0.7 pnpm add hashring@0.0.7 yarn add hashring@0.0.7
Runtime dependencies
- bisection
- simple-lru-cache 0.0.x
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.
- bisection@0.0.3 — direct
- simple-lru-cache@0.0.2 — direct
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.
| Code-Review | 1/10 — Found 4/26 approved changesets -- score normalized to 1 |
|---|---|
| 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 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy file not detected |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-02T20:52:10.928Z
- https://api.deps.dev/v3/systems/npm/packages/hashring/versions/0.0.7 — retrieved 2026-11-02T20:52:11.010Z
- https://api.deps.dev/v3/projects/github.com%2F3rd-Eden%2Fnode-hashring — retrieved 2026-11-02T14:13:49.844Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/systems/npm/packages/hashring/versions/0.0.7:dependencies — retrieved 2026-11-02T20:52:11.092Z