npmpackage.info

Gathering detailed insights and metrics for redis

Other packages similar to redis

@redis/client

5.6.0

The source code and documentation for this package are in the main [node-redis](https://github.com/redis/node-redis) repo.

redis-errors

1.2.0

Error classes used in node_redis

@redis/json

5.6.0

This package provides support for the [RedisJSON](https://redis.io/docs/data-types/json/) module, which adds JSON as a native data type to Redis.

@redis/bloom

5.6.0

This package provides support for the [RedisBloom](https://redis.io/docs/data-types/probabilistic/) module, which adds additional probabilistic data structures to Redis.

Gathering detailed insights and metrics for redis

redis - 5.6.0 | npmpackage.info

redis

Redis Node.js client

5.6.0

17,247

MIT

TypeScript

240.75 kB

5.9

Installations

npm install redis

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Min. Node Version

>= 18

Node Version

22.16.0

NPM Version

10.9.2 Score

99.3

Supply Chain

100

Quality

94.3

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

64

Total

1,053

Closed

387

Merged

602

Issues

Open

309

Total

1,911

Closed

1,602

Releases

144

redis@5.6.0

Updated on Jul 08, 2025

redis@5.5.6

Updated on Jun 06, 2025

redis@5.1.1

Updated on May 28, 2025

redis@5.1.0

Updated on May 20, 2025

redis@5.0.1

Updated on May 05, 2025

redis@5.0.0

Updated on Apr 30, 2025

View All 144 releases

Languages

TypeScript

JavaScript

Dockerfile

Shell

TypeScript (99.43%)

JavaScript (0.56%)

Dockerfile (0.01%)

Developer

redis

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

17,247 Stars

2,167 Commits

1,908 Forks

294 Watchers

24 Branches

281 Contributors

Updated on Jul 18, 2025

Maintainers

View All 281 Contributors

Package Meta Information

Latest Version

5.6.0

Package Id

redis@5.6.0

Unpacked Size

240.75 kB

Size

13.21 kB

File Count

NPM Version

10.9.2

Node Version

22.16.0

Published on

Jul 08, 2025

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@redis/bloom @redis/client @redis/json @redis/search @redis/time-series

Node-Redis

node-redis is a modern, high performance Redis client for Node.js.

How do I Redis?

Learn for free at Redis University

Build faster with the Redis Launchpad

Try the Redis Cloud

Dive in developer tutorials

Join the Redis community

Work at Redis

Installation

Start a redis via docker:

1docker run -p 6379:6379 -d redis:8.0-rc1

To install node-redis, simply:

1npm install redis

"redis" is the "whole in one" package that includes all the other packages. If you only need a subset of the commands, you can install the individual packages. See the list below.

Packages

Name	Description
`redis`	The client with all the "redis-stack" modules
`@redis/client`	The base clients (i.e `RedisClient`, `RedisCluster`, etc.)
`@redis/bloom`	Redis Bloom commands
`@redis/json`	Redis JSON commands
`@redis/search`	RediSearch commands
`@redis/time-series`	Redis Time-Series commands
`@redis/entraid`	Secure token-based authentication for Redis clients using Microsoft Entra ID

Looking for a high-level library to handle object mapping? See redis-om-node!

Usage

Basic Example

1import { createClient } from "redis";
2
3const client = await createClient()
4  .on("error", (err) => console.log("Redis Client Error", err))
5  .connect();
6
7await client.set("key", "value");
8const value = await client.get("key");
9client.destroy();

The above code connects to localhost on port 6379. To connect to a different host or port, use a connection string in the format redis[s]://[[username][:password]@][host][:port][/db-number]:

1createClient({
2  url: "redis://alice:foobared@awesome.redis.server:6380",
3});

You can also use discrete parameters, UNIX sockets, and even TLS to connect. Details can be found in the client configuration guide.

To check if the the client is connected and ready to send commands, use client.isReady which returns a boolean. client.isOpen is also available. This returns true when the client's underlying socket is open, and false when it isn't (for example when the client is still connecting or reconnecting after a network error).

Redis Commands

There is built-in support for all of the out-of-the-box Redis commands. They are exposed using the raw Redis command names (HSET, HGETALL, etc.) and a friendlier camel-cased version (hSet, hGetAll, etc.):

1// raw Redis commands
2await client.HSET("key", "field", "value");
3await client.HGETALL("key");
4
5// friendly JavaScript commands
6await client.hSet("key", "field", "value");
7await client.hGetAll("key");

Modifiers to commands are specified using a JavaScript object:

1await client.set("key", "value", {
2  EX: 10,
3  NX: true,
4});

Replies will be transformed into useful data structures:

1await client.hGetAll("key"); // { field1: 'value1', field2: 'value2' }
2await client.hVals("key"); // ['value1', 'value2']

Buffers are supported as well:

1const client = createClient().withTypeMapping({
2  [RESP_TYPES.BLOB_STRING]: Buffer
3});
4
5await client.hSet("key", "field", Buffer.from("value")); // 'OK'
6await client.hGet("key", "field"); // { field: <Buffer 76 61 6c 75 65> }
7

Unsupported Redis Commands

If you want to run commands and/or use arguments that Node Redis doesn't know about (yet!) use .sendCommand():

1await client.sendCommand(["SET", "key", "value", "NX"]); // 'OK'
2
3await client.sendCommand(["HGETALL", "key"]); // ['key1', 'field1', 'key2', 'field2']

Transactions (Multi/Exec)

Start a transaction by calling .multi(), then chaining your commands. When you're done, call .exec() and you'll get an array back with your results:

1await client.set("another-key", "another-value");
2
3const [setKeyReply, otherKeyValue] = await client
4  .multi()
5  .set("key", "value")
6  .get("another-key")
7  .exec(); // ['OK', 'another-value']

You can also watch keys by calling .watch(). Your transaction will abort if any of the watched keys change.

Blocking Commands

In v4, RedisClient had the ability to create a pool of connections using an "Isolation Pool" on top of the "main" connection. However, there was no way to use the pool without a "main" connection:

1const client = await createClient()
2  .on("error", (err) => console.error(err))
3  .connect();
4
5await client.ping(client.commandOptions({ isolated: true }));

In v5 we've extracted this pool logic into its own class—RedisClientPool:

1const pool = await createClientPool()
2  .on("error", (err) => console.error(err))
3  .connect();
4
5await pool.ping();

Pub/Sub

See the Pub/Sub overview.

Scan Iterator

SCAN results can be looped over using async iterators:

1for await (const key of client.scanIterator()) {
2  // use the key!
3  await client.get(key);
4}

This works with HSCAN, SSCAN, and ZSCAN too:

1for await (const { field, value } of client.hScanIterator("hash")) {
2}
3for await (const member of client.sScanIterator("set")) {
4}
5for await (const { score, value } of client.zScanIterator("sorted-set")) {
6}

You can override the default options by providing a configuration object:

1client.scanIterator({
2  TYPE: "string", // `SCAN` only
3  MATCH: "patter*",
4  COUNT: 100,
5});

Disconnecting

The QUIT command has been deprecated in Redis 7.2 and should now also be considered deprecated in Node-Redis. Instead of sending a QUIT command to the server, the client can simply close the network connection.

client.QUIT/quit() is replaced by client.close(). and, to avoid confusion, client.disconnect() has been renamed to client.destroy().

1client.destroy();

Client Side Caching

Node Redis v5 adds support for Client Side Caching, which enables clients to cache query results locally. The Redis server will notify the client when cached results are no longer valid.

1// Enable client side caching with RESP3
2const client = createClient({
3  RESP: 3, 
4  clientSideCache: {
5    ttl: 0,             // Time-to-live (0 = no expiration)
6    maxEntries: 0,      // Maximum entries (0 = unlimited)
7    evictPolicy: "LRU"  // Eviction policy: "LRU" or "FIFO"
8  }
9});

See the V5 documentation for more details and advanced usage.

Auto-Pipelining

Node Redis will automatically pipeline requests that are made during the same "tick".

1client.set("Tm9kZSBSZWRpcw==", "users:1");
2client.sAdd("users:1:tokens", "Tm9kZSBSZWRpcw==");

Of course, if you don't do something with your Promises you're certain to get unhandled Promise exceptions. To take advantage of auto-pipelining and handle your Promises, use Promise.all().

1await Promise.all([
2  client.set("Tm9kZSBSZWRpcw==", "users:1"),
3  client.sAdd("users:1:tokens", "Tm9kZSBSZWRpcw=="),
4]);

Programmability

See the Programmability overview.

Clustering

Check out the Clustering Guide when using Node Redis to connect to a Redis Cluster.

Events

The Node Redis client class is an Nodejs EventEmitter and it emits an event each time the network status changes:

Name	When	Listener arguments
`connect`	Initiating a connection to the server	No arguments
`ready`	Client is ready to use	No arguments
`end`	Connection has been closed (via `.disconnect()`)	No arguments
`error`	An error has occurred—usually a network issue such as "Socket closed unexpectedly"	`(error: Error)`
`reconnecting`	Client is trying to reconnect to the server	No arguments
`sharded-channel-moved`	See here	See here

:warning: You MUST listen to error events. If a client doesn't have at least one error listener registered and an error occurs, that error will be thrown and the Node.js process will exit. See the > EventEmitter docs for more details.

The client will not emit any other events beyond those listed above.

Supported Redis versions

Node Redis is supported with the following versions of Redis:

Version	Supported
8.0.z	:heavy_check_mark:
7.4.z	:heavy_check_mark:
7.2.z	:heavy_check_mark:
< 7.2	:x:

Node Redis should work with older versions of Redis, but it is not fully tested and we cannot offer support.

Migration

Contributing

If you'd like to contribute, check out the contributing guide.

Thank you to all the people who already contributed to Node Redis!

License

This repository is licensed under the "MIT" license. See LICENSE.

High

7.5/10

Summary

Node-Redis potential exponential regex in monitor mode

Affected Versions

>= 2.6.0, < 3.1.1

Patched Versions

3.1.1

10

Maintained

Determines if the project is "actively maintained".

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Security-Policy

Determines if the project has published a security policy.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

10

SAST

Determines if the project uses static code analysis.

6

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

3

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

3

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

2

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 2

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/codeql.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:45: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/codeql.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:59: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/codeql.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:72: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/codeql.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/documentation.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/documentation.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/documentation.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/documentation.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/release-drafter-bloom.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/release-drafter-bloom.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/release-drafter-entraid.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/release-drafter-entraid.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/release-drafter-json.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/release-drafter-json.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/release-drafter-search.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/release-drafter-search.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/release-drafter-time-series.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/release-drafter-time-series.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:23: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/stale-issues.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/stale-issues.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/tests.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/tests.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/tests.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/redis/node-redis/tests.yml/master?enable=pin
Warn: containerImage not pinned by hash: packages/test-utils/docker/Dockerfile:2
Warn: npmCommand not pinned by hash: .github/workflows/tests.yml:36
Info: 0 out of 11 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 5 third-party GitHubAction dependencies pinned
Info: 0 out of 1 containerImage dependencies pinned
Info: 3 out of 4 npmCommand dependencies pinned

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Fuzzing

Determines if the project uses fuzzing.

Score

5.9

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More