Vulnerability Database · npm · Package report
@vercel/otel: vulnerability history, versions and safety
@vercel/otel is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @vercel/otel 2.1.3 i
Updated on 23 Oct 2026
Good news: 2.1.3, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Niche
- Community Not enough data
What to do: Stay on 2.1.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.1.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 2.1.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 18 packages i
- Last release 4 months ago i
- Licence MIT i
Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Versions
Which versions are affected
Every version Vulert tracks for @vercel/otel, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- 1.14.2 19 Jun 2026
- 2.1.3 11 Jun 2026
- 2.1.2 08 Apr 2026
- 1.14.1 08 Apr 2026
- 2.1.1 16 Feb 2026
- 2.1.0 20 Oct 2025
- 1.14.0 20 Oct 2025
- 1.13.1 01 Oct 2025
- 2.0.1 30 Sep 2025
- 2.0.0 29 Sep 2025
- 2.0.0-2cf7cf1c-20250926110730 26 Sep 2025
- 1.13.0 06 Jun 2025
- 1.12.0 06 May 2025
- 1.11.0 11 Apr 2025
- 1.10.4 11 Mar 2025
- 1.10.3 10 Mar 2025
- 1.10.2 07 Mar 2025
- 1.10.1 24 Jan 2025
- 1.10.0 20 Aug 2024
- 1.9.2 16 Aug 2024
- 1.10.0-4d33ae0d-20240628232504 28 Jun 2024
- 1.9.1 24 Jun 2024
- 1.9.1-a50f4642-20240624231845 24 Jun 2024
- 1.9.0 24 Jun 2024
- 1.8.4 20 Jun 2024
- 1.8.3 24 May 2024
- 1.8.3-b37e732f-20240426222236 26 Apr 2024
- 1.8.2 25 Apr 2024
- 1.8.2-e734e5a9-20240425171536 25 Apr 2024
- 1.8.1 29 Mar 2024
- 1.8.1-b7bd2d7c-20240329050337 29 Mar 2024
- 1.8.0 28 Mar 2024
- 1.8.0-13c5a3d4-20240327235830 27 Mar 2024
- 1.8.0-27982b69-20240327185333 27 Mar 2024
- 1.8.0-8f4c4475-20240327181540 27 Mar 2024
- 1.7.2 27 Mar 2024
- 1.7.1 26 Mar 2024
- 1.7.1-f70cdaea-20240326003818 26 Mar 2024
- 1.7.0 26 Mar 2024
- 1.7.0-bb8f0597-20240325180505 25 Mar 2024
- 1.7.0-6f970e09-20240321224040 21 Mar 2024
- 1.7.0-0b9d1af8-20240321220934 21 Mar 2024
- 1.7.0-c60983a9-20240321215647 21 Mar 2024
- 1.7.0-2e0b3ffb-20240321205205 21 Mar 2024
- 1.6.2 20 Mar 2024
- 1.6.2-fcc2f7f7-20240320190806 20 Mar 2024
- 1.6.1 19 Mar 2024
- 1.6.1-71f76ce8-20240319192257 19 Mar 2024
- 1.6.1-380f7320-20240317051230 17 Mar 2024
- 1.6.1-c85a3e29-20240316005553 16 Mar 2024
- 1.6.0 13 Mar 2024
- 1.6.0-6114909c-20240312224032 12 Mar 2024
- 1.6.0-f42ab7bc-20240312221912 12 Mar 2024
- 1.6.0-8350b53b-20240312221439 12 Mar 2024
- 1.5.0 27 Feb 2024
- 1.5.0-6b63417d-20240227202737 27 Feb 2024
- 1.5.0-71b1412b-20240227193513 27 Feb 2024
- 1.5.0-18643059-20240227192312 27 Feb 2024
- 1.5.0-a944a662-20240227190953 27 Feb 2024
- 1.4.0 21 Feb 2024
- 1.3.1-e26a383e-20240221194233 21 Feb 2024
- 1.3.1-8e5cc8ea-20240221193849 21 Feb 2024
- 1.3.1-285b62b8-20240221185104 21 Feb 2024
- 1.3.1-58ed7f91-20240221184234 21 Feb 2024
- 1.3.0 16 Feb 2024
- 1.3.0-3750c3f4-20240216162848 16 Feb 2024
- 1.3.0-798b4c40-20240216091637 16 Feb 2024
- 1.3.0-bc65efe5-20240215234846 15 Feb 2024
- 1.3.0-f3637879-20240212171216 12 Feb 2024
- 1.3.0-75e86fe9-20240210020336 10 Feb 2024
- 1.3.0-4146921e-20240209064839 09 Feb 2024
- 1.3.0-6e36e10c-20240205201923 05 Feb 2024
- 1.3.0-30f59751-20240205200240 05 Feb 2024
- 1.2.1 02 Feb 2024
- 1.2.1-36420893-20240202015332 02 Feb 2024
- 1.2.1-c67c01a2-20240201214812 01 Feb 2024
- 1.2.1-ef121f28-20240201214046 01 Feb 2024
- 1.2.0 01 Feb 2024
- 1.2.0-edefb7b3-20240201023601 01 Feb 2024
- 1.1.0 29 Jan 2024
- 1.1.0-83ad9452-20240129193915 29 Jan 2024
- 1.0.1 29 Jan 2024
- 1.0.0 25 Jan 2024
- 1.0.0-57654ffd-20240125194853 25 Jan 2024
- 0.3.0 27 Apr 2023
- 0.2.0 17 Apr 2023
- 0.1.0 17 Apr 2023
- 0.0.17 06 Apr 2023
- 0.0.15 03 Apr 2023
- 0.0.2 24 Mar 2023
- 0.0.1 24 Mar 2023
All 91 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for @vercel/otel
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About @vercel/otel
Is @vercel/otel safe to use?
Vulert has no vulnerabilities on record for @vercel/otel in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is @vercel/otel's Vulert package health score?
Vulert scores @vercel/otel 85/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of @vercel/otel affected?
No. 2.1.3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of @vercel/otel should I use?
2.1.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does @vercel/otel have?
0 vulnerabilities are recorded for @vercel/otel in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new @vercel/otel vulnerabilities disclosed?
0 vulnerabilities were recorded for @vercel/otel in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of @vercel/otel are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor @vercel/otel for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @vercel/otel version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.