VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@hey-api/json-schema-ref-parser: vulnerability history, versions and safety

@hey-api/json-schema-ref-parser 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 @hey-api/json-schema-ref-parser vulnerabilities

Vulert verdict on @hey-api/json-schema-ref-parser 1.4.4 i

Updated on 23 Oct 2026

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

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

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

  • Current release 1.4.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 40 packages i
  • Stars 5,513 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 @hey-api/json-schema-ref-parser, 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
0.0.0-next-20260930190945 30 Sep 2026 none MIT — Details →
0.0.0-next-20260824173136 24 Aug 2026 none MIT — Details →
0.0.0-next-20260819153534 19 Aug 2026 none MIT — Details →
0.0.0-next-20260813201118 13 Aug 2026 none MIT — Details →
0.0.0-next-20260811214609 11 Aug 2026 none MIT — Details →
0.0.0-next-20260804175203 04 Aug 2026 none MIT — Details →
0.0.0-next-20260803133142 03 Aug 2026 none MIT — Details →
0.0.0-next-20260803131638 03 Aug 2026 none MIT — Details →
0.0.0-next-20260803105733 03 Aug 2026 none MIT — Details →
0.0.0-next-20260803085119 03 Aug 2026 none MIT — Details →
0.0.0-next-20260729142554 29 Jul 2026 none MIT — Details →
0.0.0-next-20260728215008 28 Jul 2026 none MIT — Details →
0.0.0-next-20260724070045 24 Jul 2026 none MIT — Details →
0.0.0-next-20260723124023 23 Jul 2026 none MIT — Details →
0.0.0-next-20260722143429 22 Jul 2026 none MIT — Details →
0.0.0-next-20260720171903 20 Jul 2026 none MIT — Details →
0.0.0-next-20260716114603 16 Jul 2026 none MIT — Details →
0.0.0-next-20260716114044 16 Jul 2026 none MIT — Details →
0.0.0-next-20260716112019 16 Jul 2026 none MIT — Details →
0.0.0-next-20260716105109 16 Jul 2026 none MIT — Details →
0.0.0-next-20260716103104 16 Jul 2026 none MIT — Details →
0.0.0-next-20260711024907 11 Jul 2026 none MIT — Details →
0.0.0-next-20260711024447 11 Jul 2026 none MIT — Details →
0.0.0-next-20260711005843 11 Jul 2026 none MIT — Details →
0.0.0-next-20260710233340 10 Jul 2026 none MIT — Details →
0.0.0-next-20260708192938 08 Jul 2026 none MIT — Details →
0.0.0-next-20260708181527 08 Jul 2026 none MIT — Details →
0.0.0-next-20260708062858 08 Jul 2026 none MIT — Details →
0.0.0-next-20260708062447 08 Jul 2026 none MIT — Details →
0.0.0-next-20260707171517 07 Jul 2026 none MIT — Details →
0.0.0-next-20260707165239 07 Jul 2026 none MIT — Details →
0.0.0-next-20260706032656 06 Jul 2026 none MIT — Details →
0.0.0-next-20260706012400 06 Jul 2026 none MIT — Details →
0.0.0-next-20260706002619 06 Jul 2026 none MIT — Details →
0.0.0-next-20260705234816 05 Jul 2026 none MIT — Details →
0.0.0-next-20260704045801 04 Jul 2026 none MIT — Details →
0.0.0-next-20260703214905 03 Jul 2026 none MIT — Details →
0.0.0-next-20260703213446 03 Jul 2026 none MIT — Details →
0.0.0-next-20260703212144 03 Jul 2026 none MIT — Details →
0.0.0-next-20260703211329 03 Jul 2026 none MIT — Details →
0.0.0-next-20260703210356 03 Jul 2026 none MIT — Details →
0.0.0-next-20260703201057 03 Jul 2026 none MIT — Details →
0.0.0-next-20260702212948 02 Jul 2026 none MIT — Details →
0.0.0-next-20260702204419 02 Jul 2026 none MIT — Details →
0.0.0-next-20260702203559 02 Jul 2026 none MIT — Details →
0.0.0-next-20260702203256 02 Jul 2026 none MIT — Details →
0.0.0-next-20260702202944 02 Jul 2026 none MIT — Details →
0.0.0-next-20260702202543 02 Jul 2026 none MIT — Details →
0.0.0-next-20260702200347 02 Jul 2026 none MIT — Details →
0.0.0-next-20260702002834 02 Jul 2026 none MIT — Details →
0.0.0-next-20260702001822 02 Jul 2026 none MIT — Details →
0.0.0-next-20260701212054 01 Jul 2026 none MIT — Details →
0.0.0-next-20260701201812 01 Jul 2026 none MIT — Details →
0.0.0-next-20260701192153 01 Jul 2026 none MIT — Details →
0.0.0-next-20260701143505 01 Jul 2026 none MIT — Details →
0.0.0-next-20260630203442 30 Jun 2026 none MIT — Details →
0.0.0-next-20260630092548 30 Jun 2026 none MIT — Details →
0.0.0-next-20260630092247 30 Jun 2026 none MIT — Details →
0.0.0-next-20260630050559 30 Jun 2026 none MIT — Details →
0.0.0-next-20260630032344 30 Jun 2026 none MIT — Details →
0.0.0-next-20260628214738 28 Jun 2026 none MIT — Details →
0.0.0-next-20260628165446 28 Jun 2026 none MIT — Details →
0.0.0-next-20260628165159 28 Jun 2026 none MIT — Details →
0.0.0-next-20260628164832 28 Jun 2026 none MIT — Details →
0.0.0-next-20260628163015 28 Jun 2026 none MIT — Details →
0.0.0-next-20260628162400 28 Jun 2026 none MIT — Details →
0.0.0-next-20260628160624 28 Jun 2026 none MIT — Details →
0.0.0-next-20260628025651 28 Jun 2026 none MIT — Details →
0.0.0-next-20260627144337 27 Jun 2026 none MIT — Details →
0.0.0-next-20260627003139 27 Jun 2026 none MIT — Details →
0.0.0-next-20260625220425 25 Jun 2026 none MIT — Details →
0.0.0-next-20260625120857 25 Jun 2026 none MIT — Details →
0.0.0-next-20260625120525 25 Jun 2026 none MIT — Details →
0.0.0-next-20260624072454 24 Jun 2026 none MIT — Details →
1.4.4 22 Jun 2026 none MIT — Details →
0.0.0-next-20260621204633 21 Jun 2026 none MIT — Details →
0.0.0-next-20260621202931 21 Jun 2026 none MIT — Details →
0.0.0-next-20260621081910 21 Jun 2026 none MIT — Details →
0.0.0-next-20260621074027 21 Jun 2026 none MIT — Details →
0.0.0-next-20260620070001 20 Jun 2026 none MIT — Details →
0.0.0-next-20260619175920 19 Jun 2026 none MIT — Details →
0.0.0-next-20260619163713 19 Jun 2026 none MIT — Details →
0.0.0-next-20260619162505 19 Jun 2026 none MIT — Details →
0.0.0-next-20260619153420 19 Jun 2026 none MIT — Details →
0.0.0-next-20260619152953 19 Jun 2026 none MIT — Details →
0.0.0-next-20260619152648 19 Jun 2026 none MIT — Details →
0.0.0-next-20260619142725 19 Jun 2026 none MIT — Details →
0.0.0-next-20260619142238 19 Jun 2026 none MIT — Details →
0.0.0-next-20260619141315 19 Jun 2026 none MIT — Details →
0.0.0-next-20260619135806 19 Jun 2026 none MIT — Details →
0.0.0-next-20260618224635 18 Jun 2026 none MIT — Details →
0.0.0-next-20260618220342 18 Jun 2026 none MIT — Details →
0.0.0-next-20260618121440 18 Jun 2026 none MIT — Details →
0.0.0-next-20260618120052 18 Jun 2026 none MIT — Details →
0.0.0-next-20260618111116 18 Jun 2026 none MIT — Details →
0.0.0-next-20260618053610 18 Jun 2026 none MIT — Details →
0.0.0-next-20260617094154 17 Jun 2026 none MIT — Details →
0.0.0-next-20260617092925 17 Jun 2026 none MIT — Details →
0.0.0-next-20260617092606 17 Jun 2026 none MIT — Details →
0.0.0-next-20260617092049 17 Jun 2026 none MIT — Details →
0.0.0-next-20260616090904 16 Jun 2026 none — — Details →
0.0.0-next-20260616060004 16 Jun 2026 none — — Details →
0.0.0-next-20260616055657 16 Jun 2026 none — — Details →
0.0.0-next-20260616033043 16 Jun 2026 none — — Details →
0.0.0-next-20260616030852 16 Jun 2026 none — — Details →
0.0.0-next-20260615102529 15 Jun 2026 none — — Details →
0.0.0-next-20260615083945 15 Jun 2026 none — — Details →
0.0.0-next-20260615083652 15 Jun 2026 none — — Details →
0.0.0-next-20260615020426 15 Jun 2026 none — — Details →
0.0.0-next-20260615013549 15 Jun 2026 none — — Details →
0.0.0-next-20260615012332 15 Jun 2026 none — — Details →
0.0.0-next-20260615005559 15 Jun 2026 none — — Details →
0.0.0-next-20260615005310 15 Jun 2026 none — — Details →
0.0.0-next-20260615004944 15 Jun 2026 none — — Details →
0.0.0-next-20260615004623 15 Jun 2026 none — — Details →
0.0.0-next-20260615003828 15 Jun 2026 none — — Details →
0.0.0-next-20260615003524 15 Jun 2026 none — — Details →
0.0.0-next-20260615001750 15 Jun 2026 none — — Details →
0.0.0-next-20260614234042 14 Jun 2026 none — — Details →
0.0.0-next-20260614090942 14 Jun 2026 none — — Details →

The newest 120 of 238 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 @hey-api/json-schema-ref-parser

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 @hey-api/json-schema-ref-parser

Is @hey-api/json-schema-ref-parser safe to use?

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

Vulert scores @hey-api/json-schema-ref-parser 87/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 @hey-api/json-schema-ref-parser affected?

No. 1.4.4, 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 @hey-api/json-schema-ref-parser should I use?

1.4.4 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 @hey-api/json-schema-ref-parser have?

0 vulnerabilities are recorded for @hey-api/json-schema-ref-parser 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 @hey-api/json-schema-ref-parser vulnerabilities disclosed?

0 vulnerabilities were recorded for @hey-api/json-schema-ref-parser 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 @hey-api/json-schema-ref-parser 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 @hey-api/json-schema-ref-parser for upcoming vulnerabilities?

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