crdt 3.1.4
Commutative Replicated Data Types for easy distributed/collaborative apps
crdt@3.1.4 was published on 2012-11-02. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is *.
All crdt versions · Permanent reference to 3.1.4 · Latest release
Package specifications
| Version | 3.1.4 |
|---|---|
| License declaration | Not declared |
| Published | 2012-11-02T12:26:02.071Z |
| Node.js requirement | * |
| 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 | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 833 |
| Repository forks | 43 |
Install crdt 3.1.4
npm install crdt@3.1.4 pnpm add crdt@3.1.4 yarn add crdt@3.1.4
Runtime dependencies
- between 0.0.0
- scuttlebutt ~4.1
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.
- between@0.0.0 — direct
- duplex@0.1.4 — indirect
- iterate@0.0.2 — indirect
- monotonic-timestamp@0.0.2 — indirect
- readable-stream@0.0.4 — indirect
- scuttlebutt@4.1.1 — direct
- stream-serializer@0.0.3 — 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.
| Code-Review | 1/10 — Found 4/28 approved changesets -- score normalized to 1 |
|---|---|
| Maintained | 0/10 — project is archived |
| 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 |
| Security-Policy | 0/10 — security policy file not detected |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| 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 |
Evidence and freshness
- https://registry.npmjs.org/crdt/3.1.4 — retrieved 2026-10-29T18:25:35.461Z
- https://api.deps.dev/v3/projects/github.com%2Fdominictarr%2Fcrdt — retrieved 2026-10-29T16:25:39.732Z
- https://api.deps.dev/v3/systems/npm/packages/crdt/versions/3.1.4 — retrieved 2026-10-29T18:25:36.117Z
- https://api.deps.dev/v3/systems/npm/packages/crdt/versions/3.1.4:dependencies — retrieved 2026-10-29T18:25:36.143Z