VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

ai: vulnerability history, versions and safety

ai is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 07 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ai vulnerabilities

Vulert verdict on ai 7.0.149 i

Updated on 23 Oct 2026

Good news: 7.0.149, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 96/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on 7.0.149 or newer. This can change: a vulnerability disclosed tomorrow can affect 7.0.149 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 7.0.149 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 07 Nov 2025 i
  • Highest CVSS 3.7 i
  • With no published fix 0 i
  • Stars 27,364 i
  • Last release this month i
  • Licence Apache-2.0 i
  • Similar names @opentelemetry/api i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 ai, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
6.0.313 22 Oct 2026 none Apache-2.0 — Details →
5.0.280 22 Oct 2026 none Apache-2.0 — Details →
7.0.149 22 Oct 2026 none Apache-2.0 — Details →
5.0.279 21 Oct 2026 none Apache-2.0 — Details →
7.0.148 21 Oct 2026 none Apache-2.0 — Details →
6.0.312 21 Oct 2026 none Apache-2.0 — Details →
7.0.147 20 Oct 2026 none Apache-2.0 — Details →
7.0.146 20 Oct 2026 none Apache-2.0 — Details →
7.0.145 19 Oct 2026 none Apache-2.0 — Details →
6.0.311 19 Oct 2026 none Apache-2.0 — Details →
7.0.144 19 Oct 2026 none Apache-2.0 — Details →
5.0.278 19 Oct 2026 none Apache-2.0 — Details →
6.0.310 19 Oct 2026 none Apache-2.0 — Details →
7.0.143 16 Oct 2026 none Apache-2.0 — Details →
6.0.309 16 Oct 2026 none Apache-2.0 — Details →
6.0.308 15 Oct 2026 none Apache-2.0 — Details →
7.0.142 15 Oct 2026 none Apache-2.0 — Details →
5.0.277 15 Oct 2026 none Apache-2.0 — Details →
6.0.307 15 Oct 2026 none Apache-2.0 — Details →
7.0.141 15 Oct 2026 none Apache-2.0 — Details →
5.0.276 14 Oct 2026 none Apache-2.0 — Details →
7.0.140 14 Oct 2026 none Apache-2.0 — Details →
6.0.306 14 Oct 2026 none Apache-2.0 — Details →
7.0.139 13 Oct 2026 none Apache-2.0 — Details →
5.0.275 13 Oct 2026 none Apache-2.0 — Details →
6.0.305 13 Oct 2026 none Apache-2.0 — Details →
6.0.304 12 Oct 2026 none Apache-2.0 — Details →
7.0.138 12 Oct 2026 none Apache-2.0 — Details →
5.0.274 12 Oct 2026 none Apache-2.0 — Details →
6.0.303 09 Oct 2026 none Apache-2.0 — Details →
7.0.137 09 Oct 2026 none Apache-2.0 — Details →
7.0.136 09 Oct 2026 none Apache-2.0 — Details →
7.0.135 08 Oct 2026 none Apache-2.0 — Details →
7.0.134 08 Oct 2026 none Apache-2.0 — Details →
7.0.133 08 Oct 2026 none Apache-2.0 — Details →
7.0.132 07 Oct 2026 none Apache-2.0 — Details →
7.0.131 07 Oct 2026 none Apache-2.0 — Details →
5.0.273 07 Oct 2026 none Apache-2.0 — Details →
6.0.302 07 Oct 2026 none Apache-2.0 — Details →
7.0.130 07 Oct 2026 none Apache-2.0 — Details →
7.0.129 06 Oct 2026 none Apache-2.0 — Details →
6.0.301 05 Oct 2026 none Apache-2.0 — Details →
7.0.128 05 Oct 2026 none Apache-2.0 — Details →
5.0.272 05 Oct 2026 none Apache-2.0 — Details →
6.0.300 01 Oct 2026 none Apache-2.0 — Details →
7.0.127 01 Oct 2026 none Apache-2.0 — Details →
7.0.126 30 Sep 2026 none Apache-2.0 — Details →
6.0.299 30 Sep 2026 none Apache-2.0 — Details →
7.0.124 30 Sep 2026 none Apache-2.0 — Details →
6.0.298 30 Sep 2026 none Apache-2.0 — Details →
5.0.271 30 Sep 2026 none Apache-2.0 — Details →
7.0.123 30 Sep 2026 none Apache-2.0 — Details →
5.0.270 30 Sep 2026 none Apache-2.0 — Details →
6.0.297 30 Sep 2026 none Apache-2.0 — Details →
7.0.122 28 Sep 2026 none Apache-2.0 — Details →
6.0.296 28 Sep 2026 none Apache-2.0 — Details →
5.0.269 28 Sep 2026 none Apache-2.0 — Details →
6.0.295 28 Sep 2026 none Apache-2.0 — Details →
7.0.120 28 Sep 2026 none Apache-2.0 — Details →
5.0.268 28 Sep 2026 none Apache-2.0 — Details →
6.0.294 28 Sep 2026 none Apache-2.0 — Details →
7.0.119 28 Sep 2026 none Apache-2.0 — Details →
7.0.118 27 Sep 2026 none Apache-2.0 — Details →
7.0.117 27 Sep 2026 none Apache-2.0 — Details →
6.0.293 27 Sep 2026 none Apache-2.0 — Details →
7.0.116 25 Sep 2026 none Apache-2.0 — Details →
5.0.267 25 Sep 2026 none Apache-2.0 — Details →
6.0.292 25 Sep 2026 none Apache-2.0 — Details →
7.0.114 24 Sep 2026 none Apache-2.0 — Details →
6.0.291 24 Sep 2026 none Apache-2.0 — Details →
5.0.266 24 Sep 2026 none Apache-2.0 — Details →
5.0.265 23 Sep 2026 none Apache-2.0 — Details →
6.0.290 23 Sep 2026 none Apache-2.0 — Details →
7.0.113 23 Sep 2026 none Apache-2.0 — Details →
6.0.289 23 Sep 2026 none Apache-2.0 — Details →
7.0.112 23 Sep 2026 none Apache-2.0 — Details →
5.0.264 23 Sep 2026 none Apache-2.0 — Details →
7.0.111 22 Sep 2026 none Apache-2.0 — Details →
7.0.110 22 Sep 2026 none Apache-2.0 — Details →
6.0.288 22 Sep 2026 none Apache-2.0 — Details →
5.0.263 22 Sep 2026 none Apache-2.0 — Details →
7.0.109 22 Sep 2026 none Apache-2.0 — Details →
5.0.262 21 Sep 2026 none Apache-2.0 — Details →
6.0.287 21 Sep 2026 none Apache-2.0 — Details →
7.0.108 21 Sep 2026 none Apache-2.0 — Details →
7.0.107 18 Sep 2026 none Apache-2.0 — Details →
5.0.261 18 Sep 2026 none Apache-2.0 — Details →
7.0.106 18 Sep 2026 none Apache-2.0 — Details →
6.0.286 18 Sep 2026 none Apache-2.0 — Details →
5.0.260 18 Sep 2026 none Apache-2.0 — Details →
6.0.285 16 Sep 2026 none Apache-2.0 — Details →
7.0.105 16 Sep 2026 none Apache-2.0 — Details →
7.0.104 16 Sep 2026 none Apache-2.0 — Details →
6.0.284 16 Sep 2026 none Apache-2.0 — Details →
5.0.259 16 Sep 2026 none Apache-2.0 — Details →
7.0.103 16 Sep 2026 none Apache-2.0 — Details →
7.0.102 15 Sep 2026 none Apache-2.0 — Details →
7.0.101 15 Sep 2026 none Apache-2.0 — Details →
6.0.283 14 Sep 2026 none Apache-2.0 — Details →
7.0.100 14 Sep 2026 none Apache-2.0 — Details →
5.0.258 14 Sep 2026 none — — Details →
5.0.257 12 Sep 2026 none — — Details →
6.0.282 12 Sep 2026 none — — Details →
7.0.99 12 Sep 2026 none — — Details →
5.0.256 11 Sep 2026 none — — Details →
7.0.98 11 Sep 2026 none — — Details →
6.0.281 11 Sep 2026 none — — Details →
7.0.97 09 Sep 2026 none — — Details →
7.0.96 09 Sep 2026 none — — Details →
6.0.280 09 Sep 2026 none — — Details →
5.0.255 09 Sep 2026 none — — Details →
6.0.279 09 Sep 2026 none — — Details →
7.0.95 09 Sep 2026 none — — Details →
5.0.254 09 Sep 2026 none — — Details →
6.0.278 08 Sep 2026 none — — Details →
7.0.94 08 Sep 2026 none — — Details →
7.0.93 04 Sep 2026 none — — Details →
5.0.253 04 Sep 2026 none — — Details →
6.0.277 04 Sep 2026 none — — Details →
7.0.92 03 Sep 2026 none — — Details →

The newest 120 of 1,612 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for ai

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-48985: Vercel's AI SDK Filetype Whitelist Bypass Vulnerability 3.7 low 5.0.52 07 Nov 2025

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About ai

Is ai safe to use?

Vulert records 1 vulnerabilities for ai in npm: 0 critical, 0 high, 0 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is ai's Vulert package health score?

Vulert scores ai 96/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 ai affected?

No. 7.0.149, 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.

How many vulnerabilities does ai have?

1 vulnerability is recorded for ai in the npm ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ai vulnerabilities disclosed?

1 vulnerability was recorded for ai in the last 12 months, and the oldest entry in this database dates to 07 Nov 2025. 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 ai 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 ai for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ai version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.