npm · npm:@opentelemetry/instrumentation-http
@opentelemetry/instrumentation-http active
OpenTelemetry instrumentation for `node:http` and `node:https` http client and server modules
The latest stable version of @opentelemetry/instrumentation-http is 0.301.2, published on 2026-11-12. Verified by Vigia on 2026-11-12.
| Latest stable version | 0.301.2 |
|---|---|
| Published | 2026-11-12 17:02:04 UTC |
| Install | npm install @opentelemetry/instrumentation-http@latest |
| Requires (engines) | {"node":">=22.15.0"} |
| Peer dependencies | @opentelemetry/api ^1.10.0 |
| Dist-tags | next: 0.34.0 canary: 0.300.0-rc.0 latest: 0.301.2 latest-2: 0.223.2 |
| License | Apache-2.0 |
| Advisories on latest version | none known |
| Last verified | 2026-11-12 17:22:09 UTC |
| Sources | api.deps.dev, registry.npmjs.org, registry.npmjs.org |
Ask your AI assistant to check this
AI models are trained up to a date, so they can be wrong about versions, deprecations and vulnerabilities. Paste this into Claude, ChatGPT, Perplexity or Cursor and it will answer with the verified data on this page:
Before answering about the npm package "@opentelemetry/instrumentation-http", check Vigia (verified, dated facts): https://vigia.coredls.cloud/v1/packages/npm/@opentelemetry/instrumentation-http . For my whole project use https://vigia.coredls.cloud/context
Using an AI coding agent every day? Connect Vigia once and it checks this by itself.
Maintenance
| Activity | active |
|---|---|
| Last stable release | 2026-11-12 17:02:04 UTC · 0 days ago |
| Stable releases in the last 12 months | 21 |
| Published versions | 235 |
Heuristic based only on release dates; it does not measure issue or security response times.
Version history
| Version | Published |
|---|---|
0.301.2 | 2026-11-12 17:02:04 UTC |
0.223.2 | 2026-11-12 16:51:51 UTC |
0.223.1 | 2026-11-09 17:08:18 UTC |
0.301.1 | 2026-11-09 17:01:27 UTC |
0.301.0 | 2026-11-05 18:34:26 UTC |
0.300.0 | 2026-10-20 18:24:32 UTC |
0.223.0 | 2026-10-06 13:40:29 UTC |
0.222.0 | 2026-08-31 16:42:13 UTC |
0.221.0 | 2026-07-21 20:04:42 UTC |
0.220.0 | 2026-07-02 21:51:00 UTC |
0.219.0 | 2026-06-11 12:37:54 UTC |
0.218.0 | 2026-05-13 08:55:17 UTC |
0.217.0 | 2026-05-06 13:11:31 UTC |
0.216.0 | 2026-04-29 18:22:42 UTC |
0.215.0 | 2026-04-17 11:27:58 UTC |
0.214.0 | 2026-03-25 15:55:10 UTC |
0.213.0 | 2026-03-03 22:36:02 UTC |
0.212.0 | 2026-02-12 18:37:45 UTC |
0.211.0 | 2026-01-21 19:23:32 UTC |
0.210.0 | 2026-01-14 17:06:08 UTC |
Showing the 20 most recent of 92 versions. JSON
Version compatibility
Newest stable version that declares support for each runtime version (from the requirements published with each version).
| Runtime | Newest compatible version |
|---|---|
node 16 | 0.57.2 |
node 18 | 0.223.2 |
node 20 | 0.223.2 |
node 22 | 0.301.2 |
node 24 | 0.301.2 |
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
Frequently asked questions
What is the latest version of @opentelemetry/instrumentation-http?
The latest stable version of @opentelemetry/instrumentation-http is 0.301.2, published on 2026-11-12. Verified by Vigia on 2026-11-12.
How do I install the latest version of @opentelemetry/instrumentation-http?
Run npm install @opentelemetry/instrumentation-http@latest. The latest stable version is 0.301.2 (verified 2026-11-12).
Is @opentelemetry/instrumentation-http deprecated?
No. @opentelemetry/instrumentation-http is not marked as deprecated in the registry.
Which Node.js version does @opentelemetry/instrumentation-http require?
@opentelemetry/instrumentation-http 0.301.2 declares this requirement: {"node":">=22.15.0"}.
Does @opentelemetry/instrumentation-http 0.301.2 have known vulnerabilities?
No known advisories affect @opentelemetry/instrumentation-http 0.301.2 according to the data Vigia checks.
Is @opentelemetry/instrumentation-http still maintained?
@opentelemetry/instrumentation-http published 21 stable releases in the last 12 months; the most recent was 0 days ago. Activity: active.
Observed changes
- hu Nov 12 2026 17:22:09 GMT+0000 (Coordinated Universal Time) — released 0.301.1 → 0.301.2
- Mon Nov 09 2026 20:17:51 GM +0000 (Coordinated Universal Time) — released 0.301.1 → 0.301.1
- Mon Nov 09 2026 17:17:42 GM +0000 (Coordinated Universal Time) — released 0.301.0 → 0.301.1
- hu Nov 05 2026 20:12:50 GMT+0000 (Coordinated Universal Time) — released 0.301.0 → 0.301.0
- hu Nov 05 2026 18:42:47 GMT+0000 (Coordinated Universal Time) — released 0.300.0 → 0.301.0
- ue Oct 20 2026 18:45:46 GMT+0000 (Coordinated Universal Time) — runtime_requirement_changed
- ue Oct 20 2026 18:45:46 GMT+0000 (Coordinated Universal Time) — released 0.223.0 → 0.300.0
- ue Oct 06 2026 14:04:19 GMT+0000 (Coordinated Universal Time) — released 0.222.0 → 0.223.0
Related packages
- @opentelemetry/api
- underscore
- is-data-descriptor
- mlly
- @jest/pattern
- postcss-modules-extract-imports
- prismjs
- big-integer
- mdast-util-mdxjs-esm
- http-signature
- validator
- async-retry
- micromark-extension-gfm-task-list-item
Badges for your README
Show the latest version, maintenance status and deprecation status of this package. Copy the Markdown:
[](https://vigia.coredls.cloud/npm/@opentelemetry/instrumentation-http) [](https://vigia.coredls.cloud/npm/@opentelemetry/instrumentation-http) [](https://vigia.coredls.cloud/npm/@opentelemetry/instrumentation-http)
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/@opentelemetry/instrumentation-http
GET https://vigia.coredls.cloud/v1/packages/npm/@opentelemetry/instrumentation-http/versions/{version}