
Security News
/Research
Fake Corepack Site Distributes Infostealer and Proxyware to Developers
A fake corepack.org site is impersonating the Node.js tool and delivers an infostealer and proxyware to developers who download it.
@sentry/opentelemetry
Advanced tools
This package allows you to send your OpenTelemetry trace data to Sentry via OpenTelemetry SpanProcessors.
If you are using @sentry/node, OpenTelemetry support is included out of the box. This package is only necessary if you
are setting up OpenTelemetry support for Sentry yourself.
npm install @sentry/opentelemetry
# Or yarn
yarn add @sentry/opentelemetry
Note that @sentry/opentelemetry depends on the following peer dependencies:
@opentelemetry/api version 1.0.0 or greater@opentelemetry/core version 1.0.0 or greater@opentelemetry/sdk-trace-base version 1.0.0 or greater, or a package that implements that, like
@opentelemetry/sdk-node.This package exposes a few building blocks you can add to your OpenTelemetry setup in order to capture OpenTelemetry traces to Sentry.
This is how you can use this in your app:
@sentry/node!setupEventContextTrace(client)SentrySampler as samplerSentrySpanProcessor as span processorSentryAsyncLocalStorageContextManager, or wrapContextManagerClass for a custom base)SentryPropagator as propagatorsetOpenTelemetryContextAsyncContextStrategy()For example, you could set this up as follows:
import * as Sentry from '@sentry/node';
import {
SentryAsyncLocalStorageContextManager,
SentryPropagator,
SentrySampler,
SentrySpanProcessor,
setupEventContextTrace,
setOpenTelemetryContextAsyncContextStrategy,
} from '@sentry/opentelemetry';
import { context, propagation, trace } from '@opentelemetry/api';
function setupSentry() {
Sentry.init({
dsn: 'xxx',
});
const client = Sentry.getClient();
setupEventContextTrace(client);
const provider = new BasicTracerProvider({
sampler: new SentrySampler(client),
});
provider.addSpanProcessor(new SentrySpanProcessor());
// Initialize the provider
trace.setGlobalTracerProvider(provider);
propagation.setGlobalPropagator(new SentryPropagator());
context.setGlobalContextManager(new SentryAsyncLocalStorageContextManager());
setOpenTelemetryContextAsyncContextStrategy();
}
A full setup example can be found in node-experimental.
SentryTracerProvider is a minimal OpenTelemetry tracer provider which creates native Sentry spans directly.
It is useful when code uses the global OpenTelemetry API and you do not need the full OpenTelemetry SDK span processor
and exporter pipeline.
import { trace } from '@opentelemetry/api';
import { SentryTracerProvider } from '@sentry/opentelemetry';
trace.setGlobalTracerProvider(new SentryTracerProvider());
const span = trace.getTracer('example').startSpan('work');
span.end();
In @sentry/node, this is the default tracer provider. To use the full OpenTelemetry SDK BasicTracerProvider
instead, opt out with:
Sentry.init({
dsn: 'xxx',
openTelemetryBasicTracerProvider: true,
});
Providing openTelemetrySpanProcessors also falls back to the full OpenTelemetry SDK provider, since custom span
processors require the SDK span pipeline. The SentryTracerProvider does not handle OpenTelemetry logs and metrics.
FAQs
Official Sentry utilities for OpenTelemetry
The npm package @sentry/opentelemetry receives a total of 17,664,682 weekly downloads. As such, @sentry/opentelemetry popularity was classified as popular.
We found that @sentry/opentelemetry demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
/Research
A fake corepack.org site is impersonating the Node.js tool and delivers an infostealer and proxyware to developers who download it.

Research
/Security News
A large-scale campaign abused GitHub Actions in compromised repositories to exploit CVE-2026-41940 in cPanel and WHM and steal server credentials.

Security News
Five frontier LLMs generated the same nonexistent package names, leaving 53 available for potential slopsquatting across PyPI and npm.