Vulnerability Database · npm · Package report

@tinacms/cli: vulnerability history, versions and safety

@tinacms/cli is a package in the npm ecosystem. Vulert records 8 vulnerabilities for it across 114 releases, from Feb 2023 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C1 H5 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
6 in the last 12 months

Most recent disclosure 09 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on @tinacms/cli 4.0.3 i

Updated on 23 Oct 2026

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

Package health score 70/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Active

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

  • Current release 4.0.3 — unaffected i
  • Vulnerabilities on record 8 over 3 years · 6 in the last year i
  • Latest disclosure 09 Oct 2026 i
  • Highest CVSS 9.6 i
  • With no published fix 0 i
  • Stars 13,837 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence Apache-2.0 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 @tinacms/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
4.0.3 19 Oct 2026 none Apache-2.0 — Details →
0.0.0-c89dfca-20261019011829 19 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-034e88f-20261018215053 18 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-abb7c15-20261016042731 16 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-5750d3b-20261015222327 15 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-e627dc9-20261015203253 15 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-411f2bc-20261015030840 15 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-3a7c39b-20261015020017 15 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-551ce56-20261015015358 15 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-0aa31f5-20261015013815 15 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-8acae77-20261014045823 14 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-3c76897-20261014033805 14 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-53ae895-20261014031644 14 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-4010161-20261014013726 14 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-787c7a9-20261014010358 14 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-dc74885-20261013230929 13 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
4.0.2 12 Oct 2026 none Apache-2.0 — Details →
0.0.0-041d3e4-20261012043306 12 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-734617a-20261008035503 08 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-ac19fbc-20261008001704 08 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-4f2758e-20261007231402 07 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-b910516-20261007222342 07 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-40fb730-20261007052500 07 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-53686ee-20261007045029 07 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-b0fb93b-20261007043306 07 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-e68550c-20261007042056 07 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
4.0.1 07 Oct 2026 none Apache-2.0 — Details →
0.0.0-d908d7f-20261006234245 06 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-8048a7e-20261006225943 06 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-f3cf692-20261006035700 06 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-5db1597-20261004231706 04 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
4.0.0 01 Oct 2026 none Apache-2.0 — Details →
0.0.0-9fb6bd8-20261001033116 01 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-23fd057-20261001025410 01 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-321b949-20261001022726 01 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-198863a-20261001004239 01 Oct 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-df21db1-20260930045008 30 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-6691ffb-20260930035657 30 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-cfc1a9a-20260930011932 30 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-e6bf2cf-20260929235433 29 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
3.1.0 23 Sep 2026 none Apache-2.0 — Details →
0.0.0-cb46575-20260922043645 22 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-0f1ea8b-20260921051822 21 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-c1acf01-20260921023836 21 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-2aacd5f-20260918050217 18 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-288244e-20260918044909 18 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-ff3088e-20260917035626 17 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-3aa7b89-20260917002650 17 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-6cd24ce-20260916234643 16 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-b5ad014-20260916043831 16 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-4a578f9-20260915065520 15 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-1cb57e3-20260915052232 15 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
3.0.0 14 Sep 2026 none Apache-2.0 — Details →
0.0.0-2a70b77-20260914051706 14 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-66e585d-20260914050232 14 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-d030d41-20260914035226 14 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
2.7.0 07 Sep 2026 H1 Apache-2.0 Yes Details →
0.0.0-37f2e6a-20260907000727 07 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-9a7092d-20260904082129 04 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-5ea1b32-20260904035336 04 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-73452a6-20260901075138 01 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-aa686c6-20260901065704 01 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-16b9ca1-20260901064358 01 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-dbd9234-20260901062407 01 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-d0593a3-20260901055825 01 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-9fa7a4f-20260901050921 01 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-f11ce74-20260901001843 01 Sep 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-bb82395-20260831093319 31 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-d6161d6-20260831073039 31 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-d340dab-20260831071009 31 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-57707bf-20260831050143 31 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-0d38acf-20260828061647 28 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-fd6aaaf-20260828013338 28 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-670a71e-20260828003033 28 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-7c21906-20260826073400 26 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-2264a16-20260826003538 26 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-f48009e-20260825053141 25 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
2.6.1 24 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-4d08c25-20260824064357 24 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-7dd8ed0-20260824055112 24 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-5544a42-20260824053458 24 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-de5c7d7-20260824035543 24 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-d7cdea7-20260824015752 24 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-e24fc0e-20260824012452 24 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-00a8b82-20260824011213 24 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-74ae2c5-20260823230658 23 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-a711b88-20260821070846 21 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-57ea7f2-20260821070211 21 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-780ab54-20260821065701 21 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-d6a0a2f-20260821063114 21 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-8d94e35-20260821041952 21 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-ce88510-20260820061405 20 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-f32ad27-20260820050831 20 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-4f90806-20260820031514 20 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-543aad0-20260820025515 20 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-705a371-20260820023159 20 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-fc8ddd4-20260819041657 19 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-195087d-20260819023810 19 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
0.0.0-41263f5-20260819021538 19 Aug 2026 C1 H4 M2 Apache-2.0 Yes Details →
2.6.0 17 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-f014558-20260817064526 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-2860f56-20260817063119 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-5050709-20260817060924 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-4061231-20260817055908 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-4b7d9b9-20260817055847 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-dcdcb48-20260817054243 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-b8c3c13-20260817054201 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-976a93c-20260817052437 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-a0a8cb3-20260817041004 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-d2ed59a-20260817040945 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-566f977-20260817033532 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-a2305be-20260817020929 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-17931b7-20260817003637 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-7e3aa63-20260817002303 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-ced8991-20260817001426 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-f4074f4-20260817000631 17 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-4ef6b6d-20260816230829 16 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-61799cf-20260816225151 16 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-b634bfc-20260816225000 16 Aug 2026 C1 H4 M2 — Yes Details →
0.0.0-8c8e297-20260814005109 14 Aug 2026 C1 H4 M2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 1
  • 2026 6

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

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 @tinacms/cli

Is @tinacms/cli safe to use?

Vulert records 8 vulnerabilities for @tinacms/cli in npm: 1 critical, 5 high, 2 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 @tinacms/cli's Vulert package health score?

Vulert scores @tinacms/cli 70/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 @tinacms/cli affected?

No. 4.0.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.

How many vulnerabilities does @tinacms/cli have?

8 vulnerabilities are recorded for @tinacms/cli in the npm ecosystem: 1 critical, 5 high, 2 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 @tinacms/cli vulnerabilities disclosed?

6 vulnerabilities were recorded for @tinacms/cli in the last 12 months, and the oldest entry in this database dates to 08 Feb 2023. 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 @tinacms/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 @tinacms/cli for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @tinacms/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.