VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

ccusage: vulnerability history, versions and safety

ccusage 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 ccusage vulnerabilities

Vulert verdict on ccusage 20.0.41 i

Updated on 23 Oct 2026

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

Package health score 99/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

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

  • Current release 20.0.41 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 19,089 i
  • Last release this month 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 ccusage, 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
20.0.41 22 Oct 2026 none MIT — Details →
20.0.40 21 Oct 2026 none MIT — Details →
20.0.39 21 Oct 2026 none MIT — Details →
20.0.38 21 Oct 2026 none MIT — Details →
20.0.37 19 Oct 2026 none MIT — Details →
20.0.36 18 Oct 2026 none MIT — Details →
20.0.35 17 Oct 2026 none MIT — Details →
20.0.34 15 Oct 2026 none MIT — Details →
20.0.33 14 Oct 2026 none MIT — Details →
20.0.32 14 Oct 2026 none MIT — Details →
20.0.31 13 Oct 2026 none MIT — Details →
20.0.30 11 Oct 2026 none MIT — Details →
20.0.29 10 Oct 2026 none MIT — Details →
20.0.28 10 Oct 2026 none MIT — Details →
20.0.26 27 Sep 2026 none MIT — Details →
20.0.24 21 Sep 2026 none MIT — Details →
20.0.23 18 Sep 2026 none MIT — Details →
20.0.22 17 Sep 2026 none MIT — Details →
20.0.21 17 Sep 2026 none MIT — Details →
20.0.20 15 Aug 2026 none MIT — Details →
20.0.19 27 Jul 2026 none MIT — Details →
20.0.18 20 Jul 2026 none MIT — Details →
20.0.17 10 Jul 2026 none MIT — Details →
20.0.16 09 Jul 2026 none MIT — Details →
20.0.14 15 Jun 2026 none MIT — Details →
20.0.13 14 Jun 2026 none MIT — Details →
20.0.12 14 Jun 2026 none MIT — Details →
20.0.11 10 Jun 2026 none MIT — Details →
20.0.10 10 Jun 2026 none MIT — Details →
20.0.9 09 Jun 2026 none MIT — Details →
20.0.8 08 Jun 2026 none MIT — Details →
20.0.7 08 Jun 2026 none MIT — Details →
20.0.6 29 May 2026 none MIT — Details →
20.0.5 25 May 2026 none MIT — Details →
20.0.4 22 May 2026 none MIT — Details →
20.0.3 22 May 2026 none MIT — Details →
20.0.2 21 May 2026 none MIT — Details →
20.0.1 20 May 2026 none MIT — Details →
20.0.0 19 May 2026 none MIT — Details →
19.0.3 17 May 2026 none MIT — Details →
19.0.2 17 May 2026 none MIT — Details →
19.0.1 17 May 2026 none MIT — Details →
19.0.0 17 May 2026 none MIT — Details →
18.0.11 19 Apr 2026 none MIT — Details →
18.0.10 10 Mar 2026 none MIT — Details →
18.0.9 06 Mar 2026 none MIT — Details →
18.0.8 24 Feb 2026 none MIT — Details →
18.0.7 24 Feb 2026 none MIT — Details →
18.0.6 23 Feb 2026 none MIT — Details →
18.0.5 09 Jan 2026 none MIT — Details →
18.0.4 09 Jan 2026 none MIT — Details →
18.0.3 09 Jan 2026 none MIT — Details →
18.0.2 09 Jan 2026 none MIT — Details →
18.0.1 09 Jan 2026 none MIT — Details →
17.2.1 03 Jan 2026 none MIT — Details →
17.2.0 11 Dec 2025 none MIT — Details →
17.1.8 09 Dec 2025 none MIT — Details →
17.1.7 08 Dec 2025 none MIT — Details →
17.1.6 17 Nov 2025 none MIT — Details →
17.1.5 14 Nov 2025 none MIT — Details →
17.1.4 08 Nov 2025 none MIT — Details →
17.1.3 07 Oct 2025 none MIT — Details →
17.1.2 04 Oct 2025 none MIT — Details →
17.1.1 01 Oct 2025 none MIT — Details →
17.1.0 29 Sep 2025 none MIT — Details →
17.0.3 25 Sep 2025 none MIT — Details →
17.0.2 18 Sep 2025 none MIT — Details →
17.0.1 18 Sep 2025 none MIT — Details →
17.0.0 18 Sep 2025 none MIT — Details →
16.2.5 15 Sep 2025 none MIT — Details →
16.2.4 11 Sep 2025 none MIT — Details →
16.2.3 02 Sep 2025 none MIT — Details →
16.2.2 02 Sep 2025 none MIT — Details →
16.2.1 02 Sep 2025 none MIT — Details →
16.2.0 23 Aug 2025 none MIT — Details →
16.1.2 22 Aug 2025 none MIT — Details →
16.1.1 20 Aug 2025 none MIT — Details →
16.1.0 20 Aug 2025 none MIT — Details →
16.0.0 20 Aug 2025 none MIT — Details →
15.10.0 19 Aug 2025 none MIT — Details →
15.9.9 17 Aug 2025 none MIT — Details →
15.9.8 17 Aug 2025 none MIT — Details →
15.9.7 15 Aug 2025 none MIT — Details →
15.9.6 15 Aug 2025 none MIT — Details →
15.9.5 13 Aug 2025 none MIT — Details →
15.9.4 12 Aug 2025 none MIT — Details →
15.9.3 11 Aug 2025 none MIT — Details →
15.9.2 10 Aug 2025 none MIT — Details →
15.9.1 09 Aug 2025 none MIT — Details →
15.9.0 09 Aug 2025 none MIT — Details →
15.8.0 07 Aug 2025 none MIT — Details →
15.7.1 04 Aug 2025 none MIT — Details →
15.7.0 04 Aug 2025 none MIT — Details →
15.6.1 04 Aug 2025 none MIT — Details →
15.6.0 03 Aug 2025 none MIT — Details →
15.5.2 24 Jul 2025 none MIT — Details →
15.5.1 22 Jul 2025 none MIT — Details →
15.5.0 19 Jul 2025 none MIT — Details →
15.4.0 19 Jul 2025 none MIT — Details →
15.3.1 06 Jul 2025 none MIT — Details →
15.3.0 04 Jul 2025 none — — Details →
15.2.0 22 Jun 2025 none — — Details →
15.1.0 22 Jun 2025 none — — Details →
15.0.1 21 Jun 2025 none — — Details →
15.0.0 21 Jun 2025 none — — Details →
14.1.2 20 Jun 2025 none — — Details →
14.1.1 20 Jun 2025 none — — Details →
14.1.0 20 Jun 2025 none — — Details →
14.0.0 20 Jun 2025 none — — Details →
13.0.1 18 Jun 2025 none — — Details →
13.0.0 18 Jun 2025 none — — Details →
12.4.0 18 Jun 2025 none — — Details →
12.3.2 18 Jun 2025 none — — Details →
12.3.1 18 Jun 2025 none — — Details →
12.3.0 18 Jun 2025 none — — Details →
12.2.0 18 Jun 2025 none — — Details →
12.1.0 17 Jun 2025 none — — Details →
12.0.0 17 Jun 2025 none — — Details →
11.0.2 17 Jun 2025 none — — Details →
11.0.1 17 Jun 2025 none — — Details →

The newest 120 of 151 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 ccusage

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 ccusage

Is ccusage safe to use?

Vulert has no vulnerabilities on record for ccusage 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 ccusage's Vulert package health score?

Vulert scores ccusage 99/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 ccusage affected?

No. 20.0.41, 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 ccusage have?

0 vulnerabilities are recorded for ccusage 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 ccusage vulnerabilities disclosed?

0 vulnerabilities were recorded for ccusage 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 ccusage 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 ccusage for upcoming vulnerabilities?

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