VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@iconify/json: vulnerability history, versions and safety

@iconify/json is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

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.

See all @iconify/json vulnerabilities

Vulert verdict on @iconify/json 2.2.546 i

Updated on 23 Oct 2026

Good news: 2.2.546, the version you would install today, has no known vulnerabilities.

Package health score 88/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 2.2.546 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 246 packages i
  • Stars 1,068 i
  • Last release this month 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 @iconify/json, 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
2.2.546 20 Oct 2026 none MIT — Details →
2.2.545 18 Oct 2026 none MIT — Details →
2.2.544 16 Oct 2026 none MIT — Details →
2.2.543 14 Oct 2026 none MIT — Details →
2.2.542 12 Oct 2026 none MIT — Details →
2.2.541 09 Oct 2026 none MIT — Details →
2.2.540 07 Oct 2026 none MIT — Details →
2.2.539 05 Oct 2026 none MIT — Details →
2.2.538 03 Oct 2026 none MIT — Details →
2.2.537 01 Oct 2026 none MIT — Details →
2.2.536 30 Sep 2026 none MIT — Details →
2.2.535 28 Sep 2026 none MIT — Details →
2.2.534 26 Sep 2026 none MIT — Details →
2.2.533 23 Sep 2026 none MIT — Details →
2.2.532 22 Sep 2026 none MIT — Details →
2.2.531 20 Sep 2026 none MIT — Details →
2.2.530 18 Sep 2026 none MIT — Details →
2.2.529 16 Sep 2026 none MIT — Details →
2.2.528 13 Sep 2026 none MIT — Details →
2.2.527 10 Sep 2026 none MIT — Details →
2.2.526 07 Sep 2026 none MIT — Details →
2.2.525 02 Sep 2026 none MIT — Details →
2.2.524 31 Aug 2026 none MIT — Details →
2.2.523 31 Aug 2026 none MIT — Details →
2.2.522 29 Aug 2026 none MIT — Details →
2.2.521 27 Aug 2026 none MIT — Details →
2.2.520 24 Aug 2026 none MIT — Details →
2.2.519 22 Aug 2026 none MIT — Details →
2.2.518 18 Aug 2026 none MIT — Details →
2.2.517 16 Aug 2026 none MIT — Details →
2.2.516 13 Aug 2026 none MIT — Details →
2.2.515 13 Aug 2026 none MIT — Details →
2.2.514 11 Aug 2026 none MIT — Details →
2.2.513 10 Aug 2026 none MIT — Details →
2.2.512 08 Aug 2026 none MIT — Details →
2.2.511 07 Aug 2026 none MIT — Details →
2.2.510 06 Aug 2026 none MIT — Details →
2.2.509 03 Aug 2026 none MIT — Details →
2.2.508 31 Jul 2026 none MIT — Details →
2.2.507 28 Jul 2026 none MIT — Details →
2.2.506 26 Jul 2026 none MIT — Details →
2.2.505 24 Jul 2026 none MIT — Details →
2.2.504 22 Jul 2026 none MIT — Details →
2.2.503 20 Jul 2026 none MIT — Details →
2.2.502 19 Jul 2026 none MIT — Details →
2.2.501 18 Jul 2026 none MIT — Details →
2.2.500 15 Jul 2026 none MIT — Details →
2.2.499 13 Jul 2026 none MIT — Details →
2.2.498 09 Jul 2026 none MIT — Details →
2.2.497 07 Jul 2026 none MIT — Details →
2.2.496 05 Jul 2026 none MIT — Details →
2.2.495 03 Jul 2026 none MIT — Details →
2.2.494 01 Jul 2026 none MIT — Details →
2.2.493 29 Jun 2026 none MIT — Details →
2.2.492 27 Jun 2026 none MIT — Details →
2.2.491 25 Jun 2026 none MIT — Details →
2.2.490 24 Jun 2026 none MIT — Details →
2.2.489 22 Jun 2026 none MIT — Details →
2.2.488 19 Jun 2026 none MIT — Details →
2.2.487 16 Jun 2026 none MIT — Details →
2.2.486 13 Jun 2026 none MIT — Details →
2.2.485 11 Jun 2026 none MIT — Details →
2.2.484 08 Jun 2026 none MIT — Details →
2.2.483 04 Jun 2026 none MIT — Details →
2.2.482 02 Jun 2026 none MIT — Details →
2.2.481 30 May 2026 none MIT — Details →
2.2.480 28 May 2026 none MIT — Details →
2.2.479 26 May 2026 none MIT — Details →
2.2.478 23 May 2026 none MIT — Details →
2.2.477 21 May 2026 none MIT — Details →
2.2.476 19 May 2026 none MIT — Details →
2.2.475 19 May 2026 none MIT — Details →
2.2.474 16 May 2026 none MIT — Details →
2.2.473 14 May 2026 none MIT — Details →
2.2.472 12 May 2026 none MIT — Details →
2.2.471 09 May 2026 none MIT — Details →
2.2.470 06 May 2026 none MIT — Details →
2.2.469 02 May 2026 none MIT — Details →
2.2.468 30 Apr 2026 none MIT — Details →
2.2.467 27 Apr 2026 none MIT — Details →
2.2.466 24 Apr 2026 none MIT — Details →
2.2.465 22 Apr 2026 none MIT — Details →
2.2.464 19 Apr 2026 none MIT — Details →
2.2.463 16 Apr 2026 none MIT — Details →
2.2.462 13 Apr 2026 none MIT — Details →
2.2.461 10 Apr 2026 none MIT — Details →
2.2.460 07 Apr 2026 none MIT — Details →
2.2.459 04 Apr 2026 none MIT — Details →
2.2.458 31 Mar 2026 none MIT — Details →
2.2.457 31 Mar 2026 none MIT — Details →
2.2.456 28 Mar 2026 none MIT — Details →
2.2.455 26 Mar 2026 none MIT — Details →
2.2.454 23 Mar 2026 none MIT — Details →
2.2.453 21 Mar 2026 none MIT — Details →
2.2.452 19 Mar 2026 none MIT — Details →
2.2.451 17 Mar 2026 none MIT — Details →
2.2.450 15 Mar 2026 none MIT — Details →
2.2.449 12 Mar 2026 none MIT — Details →
2.2.448 10 Mar 2026 none MIT — Details →
2.2.447 06 Mar 2026 none MIT — Details →
2.2.446 04 Mar 2026 none — — Details →
2.2.445 02 Mar 2026 none — — Details →
2.2.444 28 Feb 2026 none — — Details →
2.2.443 25 Feb 2026 none — — Details →
2.2.442 22 Feb 2026 none — — Details →
2.2.441 19 Feb 2026 none — — Details →
2.2.440 17 Feb 2026 none — — Details →
2.2.439 12 Feb 2026 none — — Details →
2.2.438 10 Feb 2026 none — — Details →
2.2.437 08 Feb 2026 none — — Details →
2.2.436 06 Feb 2026 none — — Details →
2.2.435 03 Feb 2026 none — — Details →
2.2.434 01 Feb 2026 none — — Details →
2.2.433 29 Jan 2026 none — — Details →
2.2.432 26 Jan 2026 none — — Details →
2.2.431 22 Jan 2026 none — — Details →
2.2.430 19 Jan 2026 none — — Details →
2.2.429 17 Jan 2026 none — — Details →
2.2.428 14 Jan 2026 none — — Details →
2.2.427 11 Jan 2026 none — — Details →

The newest 120 of 1,367 versions Vulert tracks. 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.

03 Vulnerabilities

Recorded vulnerabilities for @iconify/json

No vulnerability write-ups match this view

Search all 0 in the database →

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

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 @iconify/json

Is @iconify/json safe to use?

Vulert has no vulnerabilities on record for @iconify/json 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 @iconify/json's Vulert package health score?

Vulert scores @iconify/json 88/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 @iconify/json affected?

No. 2.2.546, 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 @iconify/json have?

0 vulnerabilities are recorded for @iconify/json 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 @iconify/json vulnerabilities disclosed?

0 vulnerabilities were recorded for @iconify/json 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 @iconify/json 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 @iconify/json for upcoming vulnerabilities?

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