VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

galenframework-cli: vulnerability history, versions and safety

galenframework-cli is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Feb 2019. 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 galenframework-cli vulnerabilities

Vulert verdict on galenframework-cli 2.4.4-build43 i

Updated on 22 Oct 2026

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

Package health score 51/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 2.4.4-build43 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 18 Feb 2019 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 17 i
  • OpenSSF scorecard 2/10 i
  • Last release 53 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 galenframework-cli, 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.4.4-build43 20 May 2022 none MIT — Details →
2.4.4-1 16 Apr 2021 none MIT — Details →
2.4.4-build1575293422 02 Dec 2019 none MIT — Details →
2.4.4-develop-165 30 Oct 2019 none MIT — Details →
2.4.4-develop-163 29 Oct 2019 none MIT — Details →
2.4.4-develop-162 24 Oct 2019 none MIT — Details →
2.4.4-feature-github-actions-2 10 Oct 2019 none MIT — Details →
2.4.4-develop-157 21 Aug 2019 none MIT — Details →
2.4.4-develop-153 09 Aug 2019 none MIT — Details →
2.4.4-develop-152 06 Aug 2019 none MIT — Details →
2.4.4-develop-151 05 Aug 2019 none MIT — Details →
2.4.4-develop-150 03 Aug 2019 none MIT — Details →
2.4.4-develop-147 02 Aug 2019 none MIT — Details →
2.4.4-develop-146 02 Aug 2019 none MIT — Details →
2.4.4-develop-145 02 Aug 2019 none MIT — Details →
2.4.4-develop-143 01 Aug 2019 none MIT — Details →
2.4.4-develop-142 15 Mar 2019 none MIT — Details →
2.4.4 15 Mar 2019 none MIT — Details →
2.4.4-develop-141 15 Mar 2019 none MIT — Details →
2.4.3-develop-140 15 Mar 2019 none MIT — Details →
2.4.3-develop-139 10 Mar 2019 none MIT — Details →
2.4.3-develop-138 10 Mar 2019 none MIT — Details →
2.4.3-develop-137 19 Feb 2019 none MIT — Details →
2.4.3-develop-136 18 Feb 2019 none MIT — Details →
2.4.3-develop-135 18 Feb 2019 none MIT — Details →
2.4.3-develop-134 18 Feb 2019 none MIT — Details →
2.4.3 18 Feb 2019 none MIT — Details →
2.4.3-develop-133 18 Feb 2019 none MIT — Details →
2.4.2-develop-132 18 Feb 2019 none MIT — Details →
2.4.2 31 Jan 2019 none MIT — Details →
2.4.1-develop-131 31 Jan 2019 none MIT — Details →
2.4.1-develop-130 04 Jan 2019 none MIT — Details →
2.4.1-develop-129 04 Jan 2019 none MIT — Details →
2.4.1-develop-128 03 Jan 2019 none MIT — Details →
2.4.1-feature-47-nodejs-integration-1 03 Jan 2019 none MIT — Details →
2.4.1-develop-127 03 Jan 2019 none MIT — Details →
2.4.1-develop-126 03 Jan 2019 none MIT — Details →
2.4.1-develop-125 03 Jan 2019 none MIT — Details →
2.4.1-develop-124 03 Jan 2019 none MIT — Details →
2.4.1-feature-nodejs-6 03 Jan 2019 none MIT — Details →
2.4.1-develop-123 03 Jan 2019 none MIT — Details →
2.4.1-develop-122 03 Jan 2019 none MIT — Details →
2.4.1-feature-61-use-jar-1 25 Dec 2018 none MIT — Details →
2.4.1-develop-121 23 Dec 2018 none MIT — Details →
2.4.1 23 Dec 2018 none MIT — Details →
2.4.1-develop-120 23 Dec 2018 none MIT — Details →
2.4.0-develop-119 04 Nov 2018 none MIT — Details →
2.4.0-feature-safari-ext-2 04 Nov 2018 none MIT — Details →
2.4.0-feature-safari-ext-1 04 Nov 2018 none MIT — Details →
2.4.0-develop-118 04 Nov 2018 none MIT — Details →
2.4.0-develop-117 04 Nov 2018 none MIT — Details →
2.4.0-develop-116 04 Nov 2018 none MIT — Details →
2.4.0-develop-115 04 Nov 2018 none MIT — Details →
2.4.0 04 Nov 2018 none MIT — Details →
2.3.7-develop-114 04 Nov 2018 none MIT — Details →
2.3.7-develop-111 03 Nov 2018 none MIT — Details →
2.3.7-develop-110 31 Oct 2018 none MIT — Details →
2.3.7-develop-108 08 Sep 2018 none MIT — Details →
2.3.7-develop-106 08 Sep 2018 none MIT — Details →
2.3.7-develop-104 12 Aug 2018 none MIT — Details →
2.3.7-develop-103 12 Aug 2018 none MIT — Details →
2.3.7-develop-102 12 Aug 2018 none MIT — Details →
2.3.7-develop-96 20 Jul 2018 none MIT — Details →
2.3.7-develop-95 20 Jul 2018 none MIT — Details →
2.3.7-develop-90 04 Jun 2018 none MIT — Details →
2.3.7-develop-89 03 Jun 2018 none MIT — Details →
2.3.7-develop-88 28 May 2018 none MIT — Details →
2.3.7-develop-87 28 May 2018 none MIT — Details →
2.3.7-develop-86 26 May 2018 none MIT — Details →
2.3.7-develop-85 26 May 2018 none MIT — Details →
2.3.7 26 May 2018 none MIT — Details →
2.3.6-develop-75 17 Feb 2018 none MIT — Details →
2.3.6-develop-74 17 Feb 2018 none MIT — Details →
2.3.5-feature-nodejs-4 16 Feb 2018 none MIT — Details →
2.3.5-feature-nodejs-3 16 Feb 2018 none MIT — Details →
2.3.6-feature-docker-4 06 Feb 2018 none MIT — Details →
2.3.6-feature-docker-3 06 Feb 2018 none MIT — Details →
2.3.6-feature-docker-2 06 Feb 2018 none MIT — Details →
2.3.6-develop-61 22 Dec 2017 none MIT — Details →
2.3.6-develop-60 21 Dec 2017 none MIT — Details →
2.3.5-feature-nodejs-2 15 Dec 2017 none MIT — Details →
2.3.6-master-17 15 Dec 2017 none MIT — Details →
2.3.6-develop-59 15 Dec 2017 none MIT — Details →
2.3.6 15 Dec 2017 none MIT — Details →
2.3.5-develop-58 15 Dec 2017 none MIT — Details →
2.3.5-develop-57 17 Nov 2017 none MIT — Details →
2.3.5-feature-nodejs-1 17 Nov 2017 none MIT — Details →
2.3.5-develop-56 17 Nov 2017 none MIT — Details →
2.3.5-develop-55 17 Nov 2017 none MIT — Details →
2.3.5-develop-54 17 Nov 2017 none MIT — Details →
2.3.5-develop-53 17 Nov 2017 none MIT — Details →
2.3.5-feature-47-nodejs-exports-6 17 Nov 2017 none MIT — Details →
2.3.5-develop-52 14 Nov 2017 none MIT — Details →
2.3.5-develop-50 12 Nov 2017 none MIT — Details →
2.3.5-feature-47-nodejs-exports-5 22 Oct 2017 none MIT — Details →
2.3.5-feature-47-nodejs-exports-4 21 Oct 2017 none MIT — Details →
2.3.5-develop-49 18 Oct 2017 none MIT — Details →
2.3.5-feature-47-nodejs-exports-1 10 Oct 2017 none MIT — Details →
2.3.5-develop-48 04 Oct 2017 none MIT — Details →
2.3.5-develop-47 07 Sep 2017 none MIT — Details →
2.3.5-develop-46 07 Sep 2017 none — — Details →
2.3.5-master-16 07 Sep 2017 none — — Details →
2.3.5-develop-45 07 Sep 2017 none — — Details →
2.3.5 07 Sep 2017 none — — Details →
2.3.4-develop-44 07 Sep 2017 none — — Details →
2.3.4-develop-43 07 Sep 2017 none — — Details →
2.3.4-develop-42 11 Aug 2017 none — — Details →
2.3.4-develop-36 26 Jul 2017 none — — Details →
2.3.4-develop-35 05 Jul 2017 none — — Details →
2.3.4-develop-34 14 Jun 2017 none — — Details →
2.3.4-develop-33 14 Jun 2017 none — — Details →
2.3.4-master-15 14 Jun 2017 none — — Details →
2.3.4-develop-32 14 Jun 2017 none — — Details →
2.3.4-master-14 14 Jun 2017 none — — Details →
2.3.4-master-13 14 Jun 2017 none — — Details →
2.3.4-master-12 14 Jun 2017 none — — Details →
2.3.4 14 Jun 2017 none — — Details →
2.3.4-develop-31 14 Jun 2017 none — — Details →
2.3.3-develop-30 13 Jun 2017 none — — Details →
2.3.3-develop-29 06 Jun 2017 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 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 galenframework-cli

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-10560: Insecure Download of Executable in galenframework-cli N/A high 2.3.1 18 Feb 2019

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 galenframework-cli

Is galenframework-cli safe to use?

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

Vulert scores galenframework-cli 51/100, which reads as usable, but worth attention. 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 galenframework-cli affected?

No. 2.4.4-build43, 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 galenframework-cli should I use?

2.4.4-build43 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 galenframework-cli have?

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

0 vulnerabilities were recorded for galenframework-cli in the last 12 months, and the oldest entry in this database dates to 18 Feb 2019. 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 galenframework-cli 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 galenframework-cli for upcoming vulnerabilities?

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