npm · npm:@opentelemetry/instrumentation-mysql
@opentelemetry/instrumentation-mysql active
OpenTelemetry instrumentation for `mysql` database client for MySQL
The latest stable version of @opentelemetry/instrumentation-mysql is 0.71.0, published on 2026-11-05. Verified by Vigia on 2026-11-12.
| Latest stable version | 0.71.0 |
|---|---|
| Published | 2026-11-05 21:38:05 UTC |
| Install | npm install @opentelemetry/instrumentation-mysql@latest |
| Requires (engines) | {"node":">=22.15.0"} |
| Peer dependencies | @opentelemetry/api ^1.10.0 |
| Dist-tags | latest: 0.71.0 |
| License | Apache-2.0 |
| Advisories on latest version | none known |
| Last verified | 2026-11-12 12:57:10 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-mysql", check Vigia (verified, dated facts): https://vigia.coredls.cloud/v1/packages/npm/@opentelemetry/instrumentation-mysql . 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-10-20 21:15:00 UTC · 23 days ago |
| Stable releases in the last 12 months | 17 |
| Published versions | 70 |
Heuristic based only on release dates; it does not measure issue or security response times.
Version history
| Version | Published |
|---|---|
0.70.0 | 2026-10-20 21:15:00 UTC |
0.69.1 | 2026-10-15 20:59:39 UTC |
0.69.0 | 2026-10-06 15:23:22 UTC |
0.68.0 | 2026-08-31 20:39:41 UTC |
0.67.0 | 2026-07-23 17:57:45 UTC |
0.66.0 | 2026-07-03 08:32:37 UTC |
0.65.0 | 2026-06-11 14:55:02 UTC |
0.64.0 | 2026-05-13 10:31:20 UTC |
0.63.0 | 2026-05-06 14:31:03 UTC |
0.62.0 | 2026-04-29 19:30:12 UTC |
0.61.0 | 2026-04-17 14:41:52 UTC |
0.60.0 | 2026-03-26 00:24:38 UTC |
0.59.0 | 2026-03-04 17:11:43 UTC |
0.58.0 | 2026-02-17 07:37:53 UTC |
0.57.0 | 2026-01-22 10:02:01 UTC |
0.56.0 | 2026-01-15 10:24:55 UTC |
0.55.0 | 2025-12-17 23:01:24 UTC |
0.54.0 | 2025-11-06 18:01:20 UTC |
0.53.0 | 2025-10-21 16:01:15 UTC |
0.52.0 | 2025-10-06 19:10:38 UTC |
Showing the 20 most recent of 70 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.45.1 |
node 18 | 0.69.1 |
node 20 | 0.69.1 |
node 22 | 0.70.0 |
node 24 | 0.70.0 |
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-mysql?
The latest stable version of @opentelemetry/instrumentation-mysql is 0.71.0, published on 2026-11-05. Verified by Vigia on 2026-11-12.
How do I install the latest version of @opentelemetry/instrumentation-mysql?
Run npm install @opentelemetry/instrumentation-mysql@latest. The latest stable version is 0.71.0 (verified 2026-11-12).
Is @opentelemetry/instrumentation-mysql deprecated?
No. @opentelemetry/instrumentation-mysql is not marked as deprecated in the registry.
Which Node.js version does @opentelemetry/instrumentation-mysql require?
@opentelemetry/instrumentation-mysql 0.71.0 declares this requirement: {"node":">=22.15.0"}.
Does @opentelemetry/instrumentation-mysql 0.71.0 have known vulnerabilities?
No known advisories affect @opentelemetry/instrumentation-mysql 0.71.0 according to the data Vigia checks.
Is @opentelemetry/instrumentation-mysql still maintained?
@opentelemetry/instrumentation-mysql published 17 stable releases in the last 12 months; the most recent was 23 days ago. Activity: active.
Observed changes
- Fri Nov 06 2026 12:48:34 GM +0000 (Coordinated Universal Time) — released 0.71.0 → 0.71.0
- hu Nov 05 2026 21:47:34 GMT+0000 (Coordinated Universal Time) — released 0.70.0 → 0.71.0
- Wed Oct 21 2026 11:17:40 GM +0000 (Coordinated Universal Time) — released 0.70.0 → 0.70.0
- ue Oct 20 2026 21:16:31 GMT+0000 (Coordinated Universal Time) — runtime_requirement_changed
- ue Oct 20 2026 21:16:31 GMT+0000 (Coordinated Universal Time) — released 0.69.1 → 0.70.0
- Fri Oct 16 2026 10:49:11 GM +0000 (Coordinated Universal Time) — released 0.69.1 → 0.69.1
- hu Oct 15 2026 21:17:59 GMT+0000 (Coordinated Universal Time) — released 0.69.0 → 0.69.1
- Wed Oct 07 2026 10:09:24 GM +0000 (Coordinated Universal Time) — released 0.69.0 → 0.69.0
- ue Oct 06 2026 15:35:25 GMT+0000 (Coordinated Universal Time) — released 0.68.0 → 0.69.0
Related packages
- @opentelemetry/api
- hastscript
- node-exports-info
- @types/node-fetch
- agentkeepalive
- @emotion/serialize
- formidable
- @popperjs/core
- @opentelemetry/instrumentation-mongoose
- vite-node
- @opentelemetry/sdk-trace-node
- has-value
- aproba
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-mysql) [](https://vigia.coredls.cloud/npm/@opentelemetry/instrumentation-mysql) [](https://vigia.coredls.cloud/npm/@opentelemetry/instrumentation-mysql)
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/@opentelemetry/instrumentation-mysql
GET https://vigia.coredls.cloud/v1/packages/npm/@opentelemetry/instrumentation-mysql/versions/{version}