kurrent-io/KurrentDB-Client-NodeJS
59.5
Adequate · 8 November 2026
10k
lines of production code
TypeScript
primary language
7
measurements over time
What this system is
Features
Add OpenTelemetry instrumentation for KurrentDB client operations
This change introduces a new OpenTelemetry instrumentation package for the KurrentDB client, enabling automatic distributed tracing for database interactions. It instruments key client methods including \appendToStream\, \multiStreamAppend\, \appendRecords\, and various subscription methods (\subscribeToStream\, \subscribeToAll\, \subscribeToPersistentSubscriptionToStream\, \subscribeToPersistentSubscriptionToAll\). The instrumentation creates spans with specific attributes such as stream names, server addresses, authentication kinds (basic, bearer, provider), and operation types, allowing users to monitor and debug their KurrentDB usage within their OpenTelemetry observability stack.
packages/opentelemetry/src · high confidence
Add projection management API to the database client
The \packages/db-client/src/projections\ module now exposes a complete set of methods for managing projections via the gRPC \ProjectionsService\. Users can create continuous projections with support for the V2 engine (opt-in), update queries and emit settings, delete projections (including emitted streams and state), enable/disable/abort/reset them, and retrieve their status, result, or state. The implementation handles both gRPC and HTTP fallbacks for compatibility and maps detailed projection statistics into a structured \ProjectionDetails\ type.
packages/db-client/src/projections · high confidence
Added benchmark suite for KurrentDB and EventStoreDB clients
A new benchmarking package has been introduced to measure the performance of stream reading operations. It includes scripts for the KurrentDB client, the KurrentDB bridge client, and the legacy EventStoreDB client (v6.2.1), alongside a Docker Compose configuration to spin up a local EventStoreDB instance for testing. This allows users to compare the throughput and latency of different client implementations against a standardized read-stream workload.
packages/benchmark · high confidence
Generated KurrentDB v1 protocol bindings added
The db-client now includes generated TypeScript definitions and JavaScript stubs for the KurrentDB protocols v1 API. This adds client support for the Gossip service (cluster read), the Operations service (scavenge, shutdown, merge indexes, resign node, set node priority, restart persistent subscriptions), and the Persistent Subscriptions service, enabling the client to communicate with the server using the v1 protocol structure.
packages/db-client/generated, packages/db-client/protos · high confidence
Initial release of the KurrentDB client library types and constants
This change introduces the foundational type definitions, constants, and export structure for the new KurrentDB client library. It establishes the core data models for events (including JSON and binary types, metadata handling, and link events), stream operations (such as append states, revisions, and positions), and persistent subscriptions. The update also defines system stream names, projection engine versions (v1 and v2), and credential interfaces, providing the necessary TypeScript contracts for interacting with the KurrentDB server.
packages/db-client/src/types · high confidence
New stream management and metadata operations
The \packages/db-client/src/streams\ module now exposes new methods for managing stream lifecycle and metadata. Users can soft-delete streams with \deleteStream\ and permanently remove them with \tombstoneStream\, both supporting expected revision checks. Stream metadata can now be read via \getStreamMetadata\ and written via \setStreamMetadata\. Additionally, the \readAll\ operation now supports server-side filtering via a \filter\ option, allowing users to filter events or streams by prefix or regex directly on the server.
packages/db-client/src/streams · high confidence
New stream reading utilities and metadata helpers
This change introduces new utility classes and functions in the db-client to enhance stream interaction. The \ReadStream\ class provides a transform stream for reading events from a gRPC stream, handling confirmation and stream-not-found errors. The \Subscription\ class extends this to support subscription-based reading, emitting \caughtUp\ and \fellBehind\ events with position details, and handling checkpoint callbacks. Additionally, \streamMetadata.ts\ adds helpers to prepare and read stream metadata, including system-level settings like max age, max count, cache control, and ACLs. Finally, \systemStreams.ts\ provides utilities to identify system streams and metastreams.
packages/db-client/src/streams/utils · high confidence
New utility module for error handling, credentials, and event conversion
The \packages/db-client/src/utils\ directory has been populated with a comprehensive set of utility modules to support the client's core operations. This includes a robust error handling system (\CommandError.ts\, \convertBridgeError.ts\) that maps gRPC and native bridge errors to specific, typed exceptions (e.g., \NotLeaderError\, \StreamNotFoundError\) with extracted metadata. Credential management is standardized via \credentials.ts\, which provides type predicates and header generation for both Basic and Bearer authentication. Event processing is supported by \convertGrpcEvent.ts\ and \convertRustEvent.ts\, which handle the translation of gRPC and Rust bridge events into the client's internal \ResolvedEvent\ format, including proper handling of JSON metadata and BigInt positions. Additional utilities cover stream identification, UUID parsing, backpressured writes, and debug logging.
packages/db-client/src/utils · high confidence
Persistent subscription management and streaming capabilities
The database client now exposes a comprehensive set of methods for managing persistent subscriptions, including creating, updating, and deleting subscriptions for both specific streams and the global $all stream. Users can retrieve subscription information, list existing subscriptions, and restart the subscription subsystem. Additionally, the client supports subscribing to persistent subscriptions to receive real-time event streams, with built-in support for acknowledging (ack) and negatively acknowledging (nack) events, including options to park, retry, skip, or stop processing. The implementation handles protocol versioning, automatically falling back to HTTP for older servers where gRPC is not supported, and enforces server version requirements for specific features like the PinnedByCorrelation consumer strategy.
packages/db-client/src/persistentSubscription · high confidence
Behavioural changes
Introduce v2-based multi-stream and batch append operations with strict metadata validation
The \appendToStream\ module now supports three distinct append modes: \batchAppend\ (v1 protocol, used when available for single-stream batching), \multiStreamAppend\ (v2 protocol, enabling atomic writes across multiple streams via the \appendSession\ RPC), and \appendRecords\ (v2 protocol, allowing interleaved records with cross-stream consistency checks). A key behavioral change is the enforcement of strict metadata validation for \multiStreamAppend\ and \appendRecords\: metadata must be plain objects with string keys and string values; non-string values, arrays, or raw Uint8Arrays will now throw an error rather than being silently processed or converted. Additionally, \batchAppend\ now includes a fix to prevent unhandled promise rejections and cross-stream error contamination by properly settling promises in the error handler and using correlation IDs to match responses.
packages/db-client/src/streams/appendToStream · high confidence
Rebranded database client with TLS verification and connection string updates
The database client has been rebranded to support the Kurrent database, updating connection string protocols from 'esdb' to 'kurrentdb' (with a deprecation warning for the old protocol). A new 'tlsVerifyCert' option is now honored in connection strings, allowing users to disable certificate verification without switching to a fully insecure connection. The client also introduces first-class support for bearer token credentials, enabling authentication via bearer tokens in addition to existing methods.
packages/db-client/src/Client · high confidence
Test coverage
Added comprehensive test coverage for streams module; Added comprehensive tests for KurrentDB client connection handling; Added integration and unit tests for the KurrentDB client; Added integration tests for persistent subscription operations; Added sample tests for KurrentDB client operations; Added test coverage for projection management operations; Added tests for OpenTelemetry instrumentation; New test infrastructure utilities for KurrentDB client testing.
Dependencies
Initialize documentation site and monorepo structure
This change introduces the project's documentation site (\docs/\) built with VuePress 2, Vite, and Vue 3, including dependencies for syntax highlighting, search, and Mermaid diagrams. It also establishes the root monorepo configuration using Yarn 4 and Nx, defining workspace packages for the core client (\@kurrent/kurrentdb-client\), OpenTelemetry instrumentation, benchmarking, and testing utilities.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.
Score
- CAI 53 → 59 (+6.6)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 75 → 66 (-9.2)
- Architecture 89 → 88 (-1.4)
- Maturity 36 → 59 (+22.8)
- Readiness 65 → 57 (-7.8)
- Security 61 → 56 (-5.1)
- Performance 91 → 91 (+0.0)
Resolved (20)
- Ambiguous distinction between 'disable' and 'abort'. Both operate on projections and return void. 'Disable' usually means stopping future processing, while 'abort' might imply stopping current processing immediately. Without clear documentation or distinct return types (e.g., status codes), users may confuse when to use which.
- Coverage not measured — JavaScript/TypeScript suite
- Cross-context type Credentials (db-client → opentelemetry) (packages/opentelemetry/src/utils.ts)
- Documentation: other issue (docs/.vuepress/public/robots.txt)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- Highly similar naming and signature for Projection operations. getProjectionResult and getProjectionState both return Promise<T> and take a projection name. In many ES systems, 'state' and 'result' are used interchangeably or refer to the same underlying data (the current state of the projection). This creates confusion for users about which method to use.
- Hotspot: packages/db-client/src/streams/appendToStream/batchAppend.ts (packages/db-client/src/streams/appendToStream/batchAppend.ts)
- Medium CVE: [GHSA redacted] (yarn.lock)
- Medium CVE: [GHSA redacted] (yarn.lock)
- Medium CVE: [GHSA redacted] (yarn.lock)
- Off-boarding risk: anonymized user #1
- Semantic ambiguity between delete and tombstone operations. Both return DeleteResult and accept similar options (revision checks), but have distinct names. In Event Sourcing, 'tombstone' usually implies a logical delete or a specific marker event, while 'delete' might be physical or irreversible. However, the identical return type and similar option structure suggest they might be thin wrappers around the same underlying mechanism or confusingly similar operations.
- Split packages/db-client
- Workflow token permissions not restricted (.github/workflows/build-docs.yml)
- Workflow token permissions not restricted (.github/workflows/main.yml)
New (56)
- Concentrated knowledge decay
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High vulnerability: [GHSA redacted] (packages/db-client/package.json)
- High: security finding (details withheld)
- High: security finding (details withheld)
- Low CVE: [GHSA redacted] (yarn.lock)
- Medium CVE: [GHSA redacted] (yarn.lock)
- No SBOM
- No artifact signing
- No build provenance
- Off-boarding risk: anonymized user #1
- Orphaned file (packages/db-client/src/Client/ServerFeatures.ts)
- Orphaned file (packages/db-client/src/Client/discovery.ts)
- Orphaned file (packages/db-client/src/Client/parseConnectionString.ts)
- Orphaned file (packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts)
- Orphaned file (packages/db-client/src/persistentSubscription/createPersistentSubscriptionToStream.ts)
- Orphaned file (packages/db-client/src/persistentSubscription/getPersistentSubscriptionToAllInfo.ts)
- …and 36 more
Changes since last survey
- 3 commits — 2 feature/other, 1 fixes
By area
- .github/files — 1 commit
- .github/workflows — 1 commit
- packages/db-client — 1 commit
Notable commits
- fix: fix: map v2 NotLeaderNodeErrorDetails to NotLeaderError for reconnection (#530)
- change: Add npm trusted publishing (#531)
- change: Pass license key to cluster nodes in tests (#529)
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
kurrent-io/KurrentDB-Client-NodeJS was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 1f63dbac799657d7b8eb28b83aa6b68de22b2684 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-bb0cb800cd0f.