Vulnerability Database · npm · Package report

agnai: vulnerability history, versions and safety

agnai is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 0 release, first recorded in Sep 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 L2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on agnai 1.0.555 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 1.0.555 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 26 Sep 2024 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Last release 7 months ago i
  • Licence AGPL-3.0 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 agnai, 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
1.0.555 04 Mar 2026 none AGPL-3.0 — Details →
1.0.554 20 Jan 2026 none AGPL-3.0 — Details →
1.0.553 12 Jan 2026 none AGPL-3.0 — Details →
1.0.552 11 Jan 2026 none AGPL-3.0 — Details →
1.0.551 11 Jan 2026 none AGPL-3.0 — Details →
1.0.550 11 Jan 2026 none AGPL-3.0 — Details →
1.0.549 11 Jan 2026 none AGPL-3.0 — Details →
1.0.548 17 Nov 2025 none AGPL-3.0 — Details →
1.0.547 30 Oct 2025 none AGPL-3.0 — Details →
1.0.546 29 Oct 2025 none AGPL-3.0 — Details →
1.0.545 29 Oct 2025 none AGPL-3.0 — Details →
1.0.544 29 Oct 2025 none AGPL-3.0 — Details →
1.0.543 29 Oct 2025 none AGPL-3.0 — Details →
1.0.542 28 Oct 2025 none AGPL-3.0 — Details →
1.0.541 28 Oct 2025 none AGPL-3.0 — Details →
1.0.540 23 Oct 2025 none AGPL-3.0 — Details →
1.0.539 22 Oct 2025 none AGPL-3.0 — Details →
1.0.538 22 Oct 2025 none AGPL-3.0 — Details →
1.0.537 22 Oct 2025 none AGPL-3.0 — Details →
1.0.536 22 Oct 2025 none AGPL-3.0 — Details →
1.0.535 21 Oct 2025 none AGPL-3.0 — Details →
1.0.534 20 Oct 2025 none AGPL-3.0 — Details →
1.0.533 20 Oct 2025 none AGPL-3.0 — Details →
1.0.532 20 Oct 2025 none AGPL-3.0 — Details →
1.0.531 18 Oct 2025 none AGPL-3.0 — Details →
1.0.530 17 Oct 2025 none AGPL-3.0 — Details →
1.0.529 17 Oct 2025 none AGPL-3.0 — Details →
1.0.528 16 Oct 2025 none AGPL-3.0 — Details →
1.0.527 16 Oct 2025 none AGPL-3.0 — Details →
1.0.526 16 Oct 2025 none AGPL-3.0 — Details →
1.0.525 15 Oct 2025 none AGPL-3.0 — Details →
1.0.524 02 Oct 2025 none AGPL-3.0 — Details →
1.0.523 01 Oct 2025 none AGPL-3.0 — Details →
1.0.522 29 Sep 2025 none AGPL-3.0 — Details →
1.0.521 28 Sep 2025 none AGPL-3.0 — Details →
1.0.520 28 Sep 2025 none AGPL-3.0 — Details →
1.0.519 01 Sep 2025 none AGPL-3.0 — Details →
1.0.518 30 Aug 2025 none AGPL-3.0 — Details →
1.0.517 27 Aug 2025 none AGPL-3.0 — Details →
1.0.516 26 Aug 2025 none AGPL-3.0 — Details →
1.0.515 24 Aug 2025 none AGPL-3.0 — Details →
1.0.514 23 Aug 2025 none AGPL-3.0 — Details →
1.0.513 20 Aug 2025 none AGPL-3.0 — Details →
1.0.512 20 Aug 2025 none AGPL-3.0 — Details →
1.0.511 20 Aug 2025 none AGPL-3.0 — Details →
1.0.510 17 Aug 2025 none AGPL-3.0 — Details →
1.0.509 17 Aug 2025 none AGPL-3.0 — Details →
1.0.508 16 Aug 2025 none AGPL-3.0 — Details →
1.0.507 10 Aug 2025 none AGPL-3.0 — Details →
1.0.506 10 Aug 2025 none AGPL-3.0 — Details →
1.0.505 09 Aug 2025 none AGPL-3.0 — Details →
1.0.504 07 Aug 2025 none AGPL-3.0 — Details →
1.0.503 04 Aug 2025 none AGPL-3.0 — Details →
1.0.502 03 Aug 2025 none AGPL-3.0 — Details →
1.0.501 03 Aug 2025 none AGPL-3.0 — Details →
1.0.500 27 Jul 2025 none AGPL-3.0 — Details →
1.0.499 27 Jul 2025 none AGPL-3.0 — Details →
1.0.498 27 Jul 2025 none AGPL-3.0 — Details →
1.0.497 26 Jul 2025 none AGPL-3.0 — Details →
1.0.496 26 Jul 2025 none AGPL-3.0 — Details →
1.0.495 26 Jul 2025 none AGPL-3.0 — Details →
1.0.494 12 Jul 2025 none AGPL-3.0 — Details →
1.0.493 11 Jul 2025 none AGPL-3.0 — Details →
1.0.492 11 Jul 2025 none AGPL-3.0 — Details →
1.0.491 11 Jul 2025 none AGPL-3.0 — Details →
1.0.490 10 Jul 2025 none AGPL-3.0 — Details →
1.0.489 10 Jul 2025 none AGPL-3.0 — Details →
1.0.488 10 Jul 2025 none AGPL-3.0 — Details →
1.0.487 10 Jul 2025 none AGPL-3.0 — Details →
1.0.486 09 Jul 2025 none AGPL-3.0 — Details →
1.0.485 03 Jul 2025 none AGPL-3.0 — Details →
1.0.484 02 Jul 2025 none AGPL-3.0 — Details →
1.0.483 02 Jul 2025 none AGPL-3.0 — Details →
1.0.482 02 Jul 2025 none AGPL-3.0 — Details →
1.0.481 02 Jul 2025 none AGPL-3.0 — Details →
1.0.480 02 Jul 2025 none AGPL-3.0 — Details →
1.0.479 29 Jun 2025 none AGPL-3.0 — Details →
1.0.478 29 Jun 2025 none AGPL-3.0 — Details →
1.0.477 29 Jun 2025 none AGPL-3.0 — Details →
1.0.476 29 Jun 2025 none AGPL-3.0 — Details →
1.0.475 29 Jun 2025 none AGPL-3.0 — Details →
1.0.474 29 Jun 2025 none AGPL-3.0 — Details →
1.0.473 29 Jun 2025 none AGPL-3.0 — Details →
1.0.472 29 Jun 2025 none AGPL-3.0 — Details →
1.0.471 23 Jun 2025 none AGPL-3.0 — Details →
1.0.470 22 Jun 2025 none AGPL-3.0 — Details →
1.0.469 21 Jun 2025 none AGPL-3.0 — Details →
1.0.468 12 Jun 2025 none AGPL-3.0 — Details →
1.0.467 12 Jun 2025 none AGPL-3.0 — Details →
1.0.466 12 Jun 2025 none AGPL-3.0 — Details →
1.0.465 10 Jun 2025 none AGPL-3.0 — Details →
1.0.464 10 Jun 2025 none AGPL-3.0 — Details →
1.0.463 10 Jun 2025 none AGPL-3.0 — Details →
1.0.462 09 Jun 2025 none AGPL-3.0 — Details →
1.0.461 09 Jun 2025 none AGPL-3.0 — Details →
1.0.460 08 Jun 2025 none AGPL-3.0 — Details →
1.0.459 08 Jun 2025 none AGPL-3.0 — Details →
1.0.458 07 Jun 2025 none AGPL-3.0 — Details →
1.0.457 07 Jun 2025 none AGPL-3.0 — Details →
1.0.456 07 Jun 2025 none AGPL-3.0 — Details →
1.0.455 07 Jun 2025 none — — Details →
1.0.454 30 May 2025 none — — Details →
1.0.453 23 May 2025 none — — Details →
1.0.452 23 May 2025 none — — Details →
1.0.451 23 May 2025 none — — Details →
1.0.450 23 May 2025 none — — Details →
1.0.449 22 May 2025 none — — Details →
1.0.448 22 May 2025 none — — Details →
1.0.447 22 May 2025 none — — Details →
1.0.446 22 May 2025 none — — Details →
1.0.445 22 May 2025 none — — Details →
1.0.444 21 May 2025 none — — Details →
1.0.443 21 May 2025 none — — Details →
1.0.442 21 May 2025 none — — Details →
1.0.441 21 May 2025 none — — Details →
1.0.440 21 May 2025 none — — Details →
1.0.439 21 May 2025 none — — Details →
1.0.438 21 May 2025 none — — Details →
1.0.437 21 May 2025 none — — Details →
1.0.436 11 May 2025 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 3

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

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 agnai

Is agnai safe to use?

Vulert records 3 vulnerabilities for agnai in npm: 1 critical, 0 high, 0 medium and 2 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 agnai's Vulert package health score?

Vulert scores agnai 73/100, which reads as in good shape. 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 agnai affected?

No. 1.0.555, 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 agnai should I use?

1.0.555 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 agnai have?

3 vulnerabilities are recorded for agnai in the npm ecosystem: 1 critical, 0 high, 0 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new agnai vulnerabilities disclosed?

0 vulnerabilities were recorded for agnai in the last 12 months, and the oldest entry in this database dates to 26 Sep 2024. 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 agnai 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 agnai for upcoming vulnerabilities?

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