Vulnerability Database · npm · Package report

hoek: vulnerability history, versions and safety

hoek is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 3 releases, first recorded in Apr 2018. 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.

Vulert verdict on hoek 6.1.3 i

Updated on 23 Oct 2026

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

Package health score 45/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Widely used
  • Community Quiet

The registry marks the latest release as deprecated, which caps this score.

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

  • Current release 6.1.3 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 26 Apr 2018 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 5,952 packages i
  • Stars 482 i
  • OpenSSF scorecard 3/10 i
  • Last release 90 months ago i
  • Licence non-standard 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 hoek, 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
4.3.1 26 Dec 2023 none non-standard — Details →
6.1.3 27 Mar 2019 none BSD-3-Clause — Details →
6.1.2 01 Dec 2018 none BSD-3-Clause — Details →
6.1.1 28 Nov 2018 none BSD-3-Clause — Details →
6.0.4 24 Nov 2018 none BSD-3-Clause — Details →
6.0.3 11 Nov 2018 none BSD-3-Clause — Details →
6.0.2 06 Nov 2018 none BSD-3-Clause — Details →
6.0.1 03 Nov 2018 none BSD-3-Clause — Details →
6.0.0 01 Nov 2018 none BSD-3-Clause — Details →
5.0.4 10 Aug 2018 none BSD-3-Clause — Details →
4.2.1 15 Feb 2018 none BSD-3-Clause — Details →
5.0.3 06 Feb 2018 none BSD-3-Clause — Details →
5.0.2 03 Nov 2017 H1 BSD-3-Clause Yes Details →
5.0.1 26 Oct 2017 H1 BSD-3-Clause Yes Details →
5.0.0 26 Sep 2017 H1 BSD-3-Clause Yes Details →
4.2.0 17 Jul 2017 none BSD-3-Clause — Details →
4.1.1 31 Mar 2017 none BSD-3-Clause — Details →
4.1.0 19 Sep 2016 none BSD-3-Clause — Details →
4.0.2 27 Jul 2016 none BSD-3-Clause — Details →
4.0.1 01 Jun 2016 none BSD-3-Clause — Details →
4.0.0 25 Apr 2016 none BSD-3-Clause — Details →
3.0.4 14 Nov 2015 none BSD-3-Clause — Details →
3.0.3 14 Nov 2015 none BSD-3-Clause — Details →
3.0.2 14 Nov 2015 none BSD-3-Clause — Details →
3.0.1 31 Oct 2015 none BSD-3-Clause — Details →
3.0.0 30 Oct 2015 none BSD-3-Clause — Details →
2.16.3 21 Sep 2015 none BSD-3-Clause — Details →
2.16.2 16 Sep 2015 none BSD-3-Clause — Details →
2.16.1 16 Sep 2015 none BSD-3-Clause — Details →
2.16.0 15 Sep 2015 none BSD-3-Clause — Details →
2.15.0 11 Sep 2015 none BSD-3-Clause — Details →
2.14.0 22 May 2015 none BSD-3-Clause — Details →
2.13.1 22 May 2015 none BSD-3-Clause — Details →
2.13.0 04 May 2015 none non-standard — Details →
2.12.0 24 Mar 2015 none non-standard — Details →
2.11.1 28 Feb 2015 none non-standard — Details →
2.11.0 05 Jan 2015 none non-standard — Details →
2.10.0 27 Nov 2014 none non-standard — Details →
2.9.1 26 Nov 2014 none non-standard — Details →
2.9.0 10 Nov 2014 none non-standard — Details →
2.8.1 23 Oct 2014 none non-standard — Details →
2.8.0 20 Oct 2014 none non-standard — Details →
2.7.0 17 Oct 2014 none non-standard — Details →
2.6.0 14 Oct 2014 none non-standard — Details →
2.5.1 10 Oct 2014 none non-standard — Details →
2.5.0 01 Oct 2014 none non-standard — Details →
2.4.1 04 Aug 2014 none non-standard — Details →
2.4.0 02 Aug 2014 none non-standard — Details →
2.3.0 29 May 2014 none non-standard — Details →
2.2.0 26 May 2014 none non-standard — Details →
2.1.1 20 May 2014 none non-standard — Details →
2.1.0 22 Apr 2014 none non-standard — Details →
2.0.0 07 Apr 2014 none non-standard — Details →
1.5.2 19 Mar 2014 none non-standard — Details →
1.5.1 06 Mar 2014 none non-standard — Details →
1.5.0 22 Feb 2014 none non-standard — Details →
1.4.1 05 Jan 2014 none non-standard — Details →
1.4.0 30 Dec 2013 none non-standard — Details →
1.3.0 22 Dec 2013 none non-standard — Details →
1.2.0 21 Nov 2013 none non-standard — Details →
1.1.2 06 Nov 2013 none non-standard — Details →
1.1.1 01 Oct 2013 none non-standard — Details →
1.1.0 29 Sep 2013 none non-standard — Details →
1.0.3 10 Sep 2013 none non-standard — Details →
1.0.2 10 Sep 2013 none non-standard — Details →
1.0.1 10 Sep 2013 none non-standard — Details →
1.0.0 20 Aug 2013 none non-standard — Details →
0.10.0 20 Aug 2013 none non-standard — Details →
0.9.1 15 May 2013 none non-standard — Details →
0.9.0 15 May 2013 none non-standard — Details →
0.8.5 04 May 2013 none non-standard — Details →
0.8.4 30 Apr 2013 none non-standard — Details →
0.8.3 29 Apr 2013 none non-standard — Details →
0.8.2 26 Apr 2013 none non-standard — Details →
0.8.1 07 Apr 2013 none non-standard — Details →
0.8.0 05 Apr 2013 none non-standard — Details →
0.7.6 04 Apr 2013 none non-standard — Details →
0.7.5 02 Apr 2013 none non-standard — Details →
0.7.4 01 Apr 2013 none non-standard — Details →
0.7.3 30 Mar 2013 none non-standard — Details →
0.7.2 29 Mar 2013 none non-standard — Details →
0.7.1 18 Mar 2013 none non-standard — Details →
0.7.0 13 Mar 2013 none non-standard — Details →
0.6.2 05 Mar 2013 none non-standard — Details →
0.6.1 05 Mar 2013 none non-standard — Details →
0.6.0 01 Mar 2013 none non-standard — Details →
0.5.0 25 Feb 2013 none non-standard — Details →
0.4.5 20 Feb 2013 none non-standard — Details →
0.4.4 17 Feb 2013 none non-standard — Details →
0.4.3 17 Feb 2013 none non-standard — Details →
0.4.2 08 Feb 2013 none non-standard — Details →
0.4.1 07 Feb 2013 none non-standard — Details →
0.4.0 05 Feb 2013 none non-standard — Details →
0.3.0 01 Feb 2013 none non-standard — Details →
0.2.0 31 Jan 2013 none non-standard — Details →
0.1.0 25 Jan 2013 none non-standard — Details →
0.0.21 02 Jan 2013 none non-standard — Details →
0.0.19 06 Dec 2012 none non-standard — Details →
0.0.18 04 Dec 2012 none non-standard — Details →
0.0.17 03 Dec 2012 none non-standard — Details →
0.0.16 30 Nov 2012 none — — Details →
0.0.15 15 Nov 2012 none — — Details →
0.0.14 13 Nov 2012 none — — Details →
0.0.13 13 Nov 2012 none — — Details →
0.0.12 13 Nov 2012 none — — Details →
0.0.11 13 Nov 2012 none — — Details →
0.0.10 15 Oct 2012 none — — Details →
0.0.9 14 Oct 2012 none — — Details →
0.0.8 14 Oct 2012 none — — Details →
0.0.7 09 Oct 2012 none — — Details →
0.0.6 21 Sep 2012 none — — Details →
0.0.5 18 Sep 2012 none — — Details →
0.0.4 18 Sep 2012 none — — Details →
0.0.3 16 Sep 2012 none — — Details →
0.0.2 16 Sep 2012 none — — Details →
0.0.1 16 Sep 2012 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 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 hoek

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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 hoek

Is hoek safe to use?

Vulert records 1 vulnerabilities for hoek 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 hoek's Vulert package health score?

Vulert scores hoek 45/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of hoek affected?

No. 6.1.3, 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 hoek should I use?

6.1.3 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 hoek have?

1 vulnerability is recorded for hoek 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 hoek vulnerabilities disclosed?

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

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