VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@hapi/hapi: vulnerability history, versions and safety

@hapi/hapi is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 6 releases, first recorded in Sep 2020. 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 H1
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 @hapi/hapi vulnerabilities

Vulert verdict on @hapi/hapi 21.4.11 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 21.4.11 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 03 Sep 2020 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 354 packages i
  • Stars 14,792 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence BSD-3-Clause 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 @hapi/hapi, 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
21.4.11 21 Oct 2026 none BSD-3-Clause — Details →
21.4.10 22 Jul 2026 none BSD-3-Clause — Details →
21.4.9 06 May 2026 none BSD-3-Clause — Details →
21.4.8 02 Apr 2026 none BSD-3-Clause — Details →
21.4.7 06 Mar 2026 none BSD-3-Clause — Details →
21.4.6 19 Feb 2026 none BSD-3-Clause — Details →
21.4.5 18 Feb 2026 none BSD-3-Clause — Details →
21.4.4 06 Nov 2025 none BSD-3-Clause — Details →
21.4.3 13 Aug 2025 none BSD-3-Clause — Details →
21.4.2 04 Aug 2025 none BSD-3-Clause — Details →
21.4.1 04 Aug 2025 none BSD-3-Clause — Details →
21.4.0 05 Mar 2025 none BSD-3-Clause — Details →
21.3.12 24 Oct 2024 none BSD-3-Clause — Details →
21.3.11 24 Oct 2024 none BSD-3-Clause — Details →
21.3.10 12 Jun 2024 none BSD-3-Clause — Details →
21.3.9 09 Apr 2024 none BSD-3-Clause — Details →
21.3.8 03 Apr 2024 none BSD-3-Clause — Details →
21.3.7 19 Mar 2024 none BSD-3-Clause — Details →
21.3.6 13 Mar 2024 none BSD-3-Clause — Details →
21.3.5 13 Mar 2024 none BSD-3-Clause — Details →
21.3.4 13 Mar 2024 none BSD-3-Clause — Details →
21.3.3 29 Jan 2024 none BSD-3-Clause — Details →
21.3.2 24 Apr 2023 none BSD-3-Clause — Details →
21.3.1 27 Mar 2023 none BSD-3-Clause — Details →
20.3.0 14 Feb 2023 none BSD-3-Clause — Details →
21.3.0 14 Feb 2023 none BSD-3-Clause — Details →
21.2.2 11 Feb 2023 none BSD-3-Clause — Details →
21.2.1 30 Jan 2023 none BSD-3-Clause — Details →
21.2.0 13 Jan 2023 none BSD-3-Clause — Details →
21.1.0 01 Dec 2022 none BSD-3-Clause — Details →
21.0.0 07 Nov 2022 none BSD-3-Clause — Details →
21.0.0-beta.1 13 Jul 2022 none BSD-3-Clause — Details →
21.0.0-beta.0 27 Jun 2022 none BSD-3-Clause — Details →
20.2.2 20 Apr 2022 none BSD-3-Clause — Details →
20.2.1 09 Oct 2021 none BSD-3-Clause — Details →
20.2.0 21 Sep 2021 none BSD-3-Clause — Details →
20.1.5 28 Jun 2021 none BSD-3-Clause — Details →
20.1.4 10 Jun 2021 none BSD-3-Clause — Details →
20.1.3 10 May 2021 none BSD-3-Clause — Details →
20.1.2 20 Mar 2021 none BSD-3-Clause — Details →
20.1.1 16 Mar 2021 none BSD-3-Clause — Details →
20.1.0 25 Jan 2021 none BSD-3-Clause — Details →
20.0.3 23 Nov 2020 none BSD-3-Clause — Details →
20.0.2 11 Nov 2020 none BSD-3-Clause — Details →
20.0.1 24 Sep 2020 none BSD-3-Clause — Details →
20.0.0 11 Aug 2020 none BSD-3-Clause — Details →
19.2.0 17 Jul 2020 none BSD-3-Clause — Details →
18.4.1 13 Feb 2020 none BSD-3-Clause — Details →
19.1.1 13 Feb 2020 none BSD-3-Clause — Details →
19.1.0 03 Feb 2020 none BSD-3-Clause — Details →
19.0.5 16 Jan 2020 none BSD-3-Clause — Details →
19.0.4 13 Jan 2020 none BSD-3-Clause — Details →
19.0.3 13 Jan 2020 none BSD-3-Clause — Details →
19.0.2 10 Jan 2020 none BSD-3-Clause — Details →
19.0.1 10 Jan 2020 none BSD-3-Clause — Details →
19.0.0 10 Jan 2020 none BSD-3-Clause — Details →
18.4.0 15 Sep 2019 H1 BSD-3-Clause Yes Details →
18.3.2 15 Aug 2019 H1 BSD-3-Clause Yes Details →
18.3.1 19 Apr 2019 H1 BSD-3-Clause Yes Details →
18.3.0 19 Apr 2019 H1 BSD-3-Clause Yes Details →
17.9.0 10 Apr 2019 H1 BSD-3-Clause Yes Details →
18.2.0 02 Apr 2019 H1 BSD-3-Clause Yes Details →

All 62 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for @hapi/hapi

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Denial of Service in @hapi/hapi N/A high 18.4.1 03 Sep 2020

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 @hapi/hapi

Is @hapi/hapi safe to use?

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

Vulert scores @hapi/hapi 84/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 @hapi/hapi affected?

No. 21.4.11, 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 @hapi/hapi have?

1 vulnerability is recorded for @hapi/hapi in the npm ecosystem: 0 critical, 1 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 @hapi/hapi vulnerabilities disclosed?

0 vulnerabilities were recorded for @hapi/hapi in the last 12 months, and the oldest entry in this database dates to 03 Sep 2020. 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 @hapi/hapi 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 @hapi/hapi for upcoming vulnerabilities?

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