Is Opentelemetry Safe?

Opentelemetry — Nerq Trust Score 83.0/100 (A- grade). Based on analysis of 2 trust dimensions, it is considered safe to use. Last updated: 2026-04-06.

Yes, Opentelemetry is safe to use. Opentelemetry is a npm package with a Nerq Trust Score of 83.0/100 (A-), based on 3 independent data dimensions. Recommended for production use. Security: 90/100. Popularity: 90/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-06. Machine-readable data (JSON).

Is Opentelemetry safe?

YES — Opentelemetry has a Nerq Trust Score of 83.0/100 (A-). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for production use — review the full report below for specific considerations.

Security Analysis → Opentelemetry Privacy Report →

What is Opentelemetry's trust score?

Opentelemetry has a Nerq Trust Score of 83.0/100, earning a A- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
90

What are the key security findings for Opentelemetry?

Opentelemetry's strongest signal is security at 90/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 90/100 — community adoption

What is Opentelemetry and who maintains it?

Authorsentry-bot
Categorynpm Packages
SourceN/A

Opentelemetry Across Platforms

Same developer/company in other registries:

sentry-opentelemetry
67/100 · gems
Sentry.OpenTelemetry
46/100 · nuget

Similar Npm by Trust Score

@supabase/supabase-js (90)@supabase/storage-js (90)@supabase/realtime-js (90)@testing-library/react (90)@supabase/functions-js (90)
See all safest Npm →

Compare

Opentelemetry vs @supabase/supabase-jsOpentelemetry vs @supabase/storage-jsOpentelemetry vs @supabase/realtime-js

Safety Guide: Opentelemetry

What is Opentelemetry?

Opentelemetry is a Node.js package — Official Sentry utilities for OpenTelemetry.

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=@sentry/opentelemetry

Key Safety Concerns for Node.js package

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Trust Assessment

Opentelemetry has a Nerq Trust Score of 83/100 (A-) and meets Nerq trust threshold. This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Detailed Score Analysis

DimensionScore
Security90/100
Privacy80/100
Reliability90/100
Transparency85/100
Maintenance60/100

Based on 5 dimensions. Data from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard.

What data does Opentelemetry collect?

Opentelemetry is a Node.js package maintained by sentry-bot. It receives approximately 8,813,572 weekly downloads. Licensed under MIT.

As a development package, Opentelemetry does not directly collect end-user personal data. However, applications built with it may collect data depending on implementation. Privacy score: 80/100.

Review the package's dependencies for potential supply chain risks. Run your package manager's audit command regularly.

Full analysis: Opentelemetry Privacy Report · Privacy review

Is Opentelemetry secure?

Security score: 90/100. Opentelemetry has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.

Licensed under MIT, allowing code inspection. Open-source packages allow independent security review of the source code.

Run your package manager's audit command (`npm audit`, `pip audit`, `cargo audit`) to check for known vulnerabilities in your dependency tree.

Full analysis: Opentelemetry Security Report

Opentelemetry Across Platforms

Same developer/company in other registries:

sentry-opentelemetry (gems, 67/100)Sentry.OpenTelemetry (nuget, 46/100)

How we calculated this score

Opentelemetry's trust score of 83.0/100 (A-) is computed from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), privacy (80/100), reliability (90/100), transparency (85/100), maintenance (60/100). Each dimension is weighted equally to produce the composite trust score.

Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.

This page was last reviewed on April 06, 2026. Data version: 1.0.

Full methodology documentation · Machine-readable data (JSON API)

Frequently Asked Questions

Is Opentelemetry Safe?
Yes, it is safe to use. @sentry/opentelemetry with a Nerq Trust Score of 83.0/100 (A-). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (90/100).
What is Opentelemetry's trust score?
@sentry/opentelemetry: 83.0/100 (A-). Score based on Security (90/100), Popularity (90/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@sentry/opentelemetry
What are safer alternatives to Opentelemetry?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. @sentry/opentelemetry scores 83.0/100.
Does Opentelemetry have known vulnerabilities?
Nerq checks Opentelemetry against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
Is Opentelemetry actively maintained?
Opentelemetry maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.

We use cookies for analytics and caching. Privacy