Gathering detailed insights and metrics for @opentelemetry/instrumentation-redis-4
Gathering detailed insights and metrics for @opentelemetry/instrumentation-redis-4
Gathering detailed insights and metrics for @opentelemetry/instrumentation-redis-4
Gathering detailed insights and metrics for @opentelemetry/instrumentation-redis-4
OpenTelemetry instrumentation for JavaScript modules
npm install @opentelemetry/instrumentation-redis-4
Typescript
Module System
Min. Node Version
Node Version
NPM Version
93.7
Supply Chain
98.1
Quality
91.7
Maintenance
100
Vulnerability
99.3
License
instrumentation-restify: v0.48.1
Updated on Jun 12, 2025
instrumentation-redis: v0.49.1
Updated on Jun 12, 2025
instrumentation-net: v0.46.1
Updated on Jun 12, 2025
instrumentation-mongodb: v0.55.1
Updated on Jun 12, 2025
instrumentation-koa: v0.50.1
Updated on Jun 12, 2025
instrumentation-hapi: v0.49.0
Updated on Jun 12, 2025
TypeScript (97.56%)
JavaScript (2.43%)
Shell (0.01%)
Total Downloads
170,702,114
Last Day
188,278
Last Week
4,443,640
Last Month
18,885,471
Last Year
138,751,530
Apache-2.0 License
800 Stars
2,327 Commits
581 Forks
16 Watchers
7 Branches
293 Contributors
Updated on Jun 13, 2025
Minified
Minified + Gzipped
Latest Version
0.49.0
Package Id
@opentelemetry/instrumentation-redis-4@0.49.0
Unpacked Size
77.20 kB
Size
18.15 kB
File Count
21
NPM Version
lerna/8.2.2/node@v18.20.8+x64 (linux)
Node Version
18.20.8
Published on
Jun 02, 2025
Cumulative downloads
Total Downloads
Last Day
9%
188,278
Compared to previous day
Last Week
-5.6%
4,443,640
Compared to previous week
Last Month
5.8%
18,885,471
Compared to previous month
Last Year
453.7%
138,751,530
Compared to previous year
3
1
Getting Started • API Documentation
Contributing • Instrumentations • Propagators • Examples
A repository for community-maintained OpenTelemetry JavaScript contributions that are not part of the core repository and core distribution of the API and the SDK.
This project includes:
Instrumentations: OpenTelemetry can collect tracing data automatically using instrumentations. Vendors/Users can also create and use their own. Please read the contributing guidelines on adding new instrumentation before opening any PRs.
Resource Detectors: OpenTelemetry can collect resource attributes of the entity that producing telemetry. For example, a process producing telemetry that is running in a container on Kubernetes has a Pod name, it is in a namespace and possibly is part of a Deployment which also has a name. All three of these attributes can be included in the Resource
.
This repository includes various components, each maintained by one or more designated component owners. Unless necessary to resolve disagreements, @open-telemetry/javascript-maintainers take a more passive role when it comes to Maintaining these components.
Component owners have the authority to make decisions on implementation and feature requests, following the best practices and the mission, vision and values of the OpenTelemetry Project. They are also assigned the Triager role to manage issues related to their components, and are the primary contact for conducting PR reviews for their components.
Component owners are automatically assigned to pull requests as reviewers. The source of truth for component ownership is .github/component_owners.yml.
Stability level for components in this repository follow the definitions in CONTRIBUTING.md.
Packages in this repository have a variable range of support for Node.JS and browser versions which for each package depend on
See the README.md
files and the engines
field in the package.json
files for the respective packages for support information about that package.
See the support section in the core repository for more general information.
We'd love your help! Use tags up-for-grabs and good first issue to get started with the project. Follow CONTRIBUTING guide to report issues or submit a proposal.
Apache 2.0 - See LICENSE for more information.
No vulnerabilities found.
Reason
all changesets reviewed
Reason
update tool detected
Details
Reason
30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
SAST tool is run on all commits
Details
Reason
30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Reason
project has 42 contributing companies or organizations
Details
Reason
branch protection is not maximal on development and all release branches
Details
Reason
dependency not pinned by hash detected -- score normalized to 5
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
21 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-06-13T12:42:36Z
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