VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

check-branches: vulnerability history, versions and safety

check-branches is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 9 releases, first recorded in Sep 2025. 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 C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 check-branches vulnerabilities

Vulert verdict on check-branches 0.0.19 i

Updated on 23 Oct 2026

Careful: 0.0.19 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 48/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.0.19 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 30 Sep 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Stars 1 i
  • Last release 58 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 check-branches, 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.19 22 Dec 2021 C1 MIT No Details →
0.0.18 22 Dec 2021 C1 MIT No Details →
0.0.17 22 Dec 2021 C1 MIT No Details →
0.0.15 22 Dec 2021 C1 MIT No Details →
0.0.14 22 Dec 2021 C1 MIT No Details →
0.0.13 22 Dec 2021 C1 MIT No Details →
0.0.12 22 Dec 2021 C1 MIT No Details →
0.0.11 22 Dec 2021 C1 MIT No Details →
0.0.1 22 Dec 2021 C1 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 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 check-branches

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-11148: Command Injection Vulnerability in check-branches Package 9.8 critical No fix published 30 Sep 2025

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 check-branches

Is check-branches safe to use?

Vulert records 1 vulnerabilities for check-branches in npm: 1 critical, 0 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is check-branches's Vulert package health score?

Vulert scores check-branches 48/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 current release has a vulnerability with no published fix, which caps this score.

Is the latest version of check-branches affected?

Yes. 0.0.19, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does check-branches have?

1 vulnerability is recorded for check-branches in the npm ecosystem: 1 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 check-branches vulnerabilities disclosed?

0 vulnerabilities were recorded for check-branches in the last 12 months, and the oldest entry in this database dates to 30 Sep 2025. 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 check-branches 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 check-branches for upcoming vulnerabilities?

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