VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@tamagui/elements: vulnerability history, versions and safety

@tamagui/elements 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 @tamagui/elements vulnerabilities

Vulert verdict on @tamagui/elements 2.7.7 i

Updated on 23 Oct 2026

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

Package health score 94/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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

  • Current release 2.7.7 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 10 packages i
  • Stars 14,260 i
  • Last release 2 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 @tamagui/elements, 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
3.0.0-beta.1216.1 11 Sep 2026 none MIT — Details →
3.0.0-beta.1215.1 11 Sep 2026 none MIT — Details →
3.0.0-beta.1213.1 11 Sep 2026 none MIT — Details →
3.0.0-beta.1212.1 11 Sep 2026 none MIT — Details →
3.0.0-beta.1209.1 11 Sep 2026 none MIT — Details →
3.0.0-beta.1202.1 11 Sep 2026 none MIT — Details →
3.0.0-beta.1191.1 11 Sep 2026 none MIT — Details →
3.0.0-beta.1187.1 11 Sep 2026 none MIT — Details →
3.0.0-beta.1177.1 11 Sep 2026 none MIT — Details →
3.0.0-beta.1173.1 11 Sep 2026 none MIT — Details →
3.0.0-beta.1169.1 10 Sep 2026 none MIT — Details →
3.0.0-beta.1161.1 10 Sep 2026 none MIT — Details →
3.0.0-beta.1153.1 10 Sep 2026 none MIT — Details →
3.0.0-beta.1149.1 10 Sep 2026 none MIT — Details →
3.0.0-beta.1141.1 10 Sep 2026 none MIT — Details →
3.0.0-beta.1133.1 09 Sep 2026 none MIT — Details →
3.0.0-beta.1125.1 09 Sep 2026 none MIT — Details →
3.0.0-beta.1123.1 09 Sep 2026 none MIT — Details →
3.0.0-beta.1121.1 09 Sep 2026 none MIT — Details →
3.0.0-beta.1115.1 09 Sep 2026 none MIT — Details →
3.0.0-beta.1111.1 09 Sep 2026 none MIT — Details →
3.0.0-beta.1109.1 09 Sep 2026 none MIT — Details →
3.0.0-beta.1101.1 08 Sep 2026 none MIT — Details →
3.0.0-beta.1099.1 08 Sep 2026 none MIT — Details →
3.0.0-beta.1097.1 08 Sep 2026 none MIT — Details →
3.0.0-beta.1093.1 07 Sep 2026 none MIT — Details →
3.0.0-beta.1091.1 07 Sep 2026 none MIT — Details →
3.0.0-beta.924.1 02 Sep 2026 none — — Details →
3.0.0-beta.922.1 02 Sep 2026 none — — Details →
2.7.7-1788328229285 02 Sep 2026 none — — Details →
3.0.0-beta.917.1 02 Sep 2026 none — — Details →
3.0.0-beta.907.1 02 Sep 2026 none — — Details →
3.0.0-beta.901.1 02 Sep 2026 none — — Details →
3.0.0-beta.891.1 01 Sep 2026 none — — Details →
3.0.0-beta.889.1 01 Sep 2026 none — — Details →
3.0.0-beta.881.1 01 Sep 2026 none — — Details →
3.0.0-beta.831.1 30 Aug 2026 none — — Details →
3.0.0-beta.807.1 29 Aug 2026 none — — Details →
3.0.0-beta.806.1 28 Aug 2026 none — — Details →
3.0.0-beta.804.1 28 Aug 2026 none — — Details →
3.0.0-beta.765.1 27 Aug 2026 none — — Details →
3.0.0-beta.755.1 26 Aug 2026 none — — Details →
3.0.0-beta.753.1 26 Aug 2026 none — — Details →
3.0.0-beta.752.1 26 Aug 2026 none — — Details →
3.0.0-beta.748.1 26 Aug 2026 none — — Details →
3.0.0-beta.745.1 26 Aug 2026 none — — Details →
3.0.0-beta.739.1 26 Aug 2026 none — — Details →
3.0.0-beta.735.1 24 Aug 2026 none — — Details →
3.0.0-beta.728.1 24 Aug 2026 none — — Details →
3.0.0-beta.719.1 23 Aug 2026 none — — Details →
3.0.0-beta.669.1 22 Aug 2026 none — — Details →
3.0.0-beta.661.1 22 Aug 2026 none — — Details →
3.0.0-beta.655.1 22 Aug 2026 none — — Details →
3.0.0-beta.653.1 22 Aug 2026 none — — Details →
3.0.0-beta.651.1 22 Aug 2026 none — — Details →
3.0.0-beta.649.1 22 Aug 2026 none — — Details →
3.0.0-beta.647.1 22 Aug 2026 none — — Details →
3.0.0-beta.645.1 22 Aug 2026 none — — Details →
3.0.0-beta.643.1 22 Aug 2026 none — — Details →
3.0.0-beta.637.1 22 Aug 2026 none — — Details →
2.7.7 15 Aug 2026 none — — Details →
2.7.6 13 Aug 2026 none — — Details →
2.7.5 13 Aug 2026 none — — Details →
2.7.4 09 Aug 2026 none — — Details →
2.7.3-1786169532869 08 Aug 2026 none — — Details →
2.7.3 08 Aug 2026 none — — Details →
2.7.2 06 Aug 2026 none — — Details →
2.7.1 05 Aug 2026 none — — Details →
2.7.0 05 Aug 2026 none — — Details →
2.6.4 05 Aug 2026 none — — Details →
2.6.3 03 Aug 2026 none — — Details →
2.6.2 31 Jul 2026 none — — Details →
2.6.1 31 Jul 2026 none — — Details →
2.6.0 28 Jul 2026 none — — Details →
2.5.3 28 Jul 2026 none — — Details →
2.5.2 28 Jul 2026 none — — Details →
2.5.1 22 Jul 2026 none — — Details →
2.5.0 21 Jul 2026 none — — Details →
2.4.6 16 Jul 2026 none — — Details →
2.4.5-1784076621864 15 Jul 2026 none — — Details →
2.4.5-1784066510418 14 Jul 2026 none — — Details →
2.4.5 11 Jul 2026 none — — Details →
2.4.4 10 Jul 2026 none — — Details →
2.4.3 09 Jul 2026 none — — Details →
2.4.2 06 Jul 2026 none — — Details →
2.4.1 04 Jul 2026 none — — Details →
2.4.0-1783110557100 03 Jul 2026 none — — Details →
2.4.0-1783099846627 03 Jul 2026 none — — Details →
2.4.0 27 Jun 2026 none — — Details →
2.3.3-1782533722506 27 Jun 2026 none — — Details →
2.3.3-1782530413169 27 Jun 2026 none — — Details →
2.3.3-1782495782270 26 Jun 2026 none — — Details →
2.3.3-1782469370633 26 Jun 2026 none — — Details →
2.3.3-1782468954742 26 Jun 2026 none — — Details →
2.3.3-1782465561627 26 Jun 2026 none — — Details →
2.3.3-1782462397214 26 Jun 2026 none — — Details →
2.3.3 23 Jun 2026 none — — Details →
2.3.2-1782110552417 22 Jun 2026 none — — Details →
2.3.2 21 Jun 2026 none — — Details →
2.3.1 18 Jun 2026 none — — Details →
2.3.0 13 Jun 2026 none — — Details →
2.2.0-1781217884154 11 Jun 2026 none — — Details →
2.2.0-1781132308330 10 Jun 2026 none — — Details →
2.2.0-1781079118220 10 Jun 2026 none — — Details →
2.2.0-1781071309197 10 Jun 2026 none — — Details →
2.2.0-1781044625560 09 Jun 2026 none — — Details →
2.2.0 09 Jun 2026 none — — Details →
2.1.0-1780964419737 09 Jun 2026 none — — Details →
2.1.0-1780670002714 05 Jun 2026 none — — Details →
2.1.0-1780645766505 05 Jun 2026 none — — Details →
2.1.0-1780546777640 04 Jun 2026 none — — Details →
2.1.0-1780536257458 04 Jun 2026 none — — Details →
2.1.0-1780520076274 03 Jun 2026 none — — Details →
2.1.0-1780426041711 02 Jun 2026 none — — Details →
2.1.0-1780288049558 01 Jun 2026 none — — Details →
2.1.0-1780182832733 30 May 2026 none — — Details →
2.1.0 30 May 2026 none — — Details →
2.0.0-1780094816896 29 May 2026 none — — Details →
2.0.0-1780092121346 29 May 2026 none — — Details →
2.0.0-1780064412517 29 May 2026 none — — Details →

The newest 120 of 908 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 @tamagui/elements

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 @tamagui/elements

Is @tamagui/elements safe to use?

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

Vulert scores @tamagui/elements 94/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 @tamagui/elements affected?

No. 2.7.7, 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 @tamagui/elements should I use?

2.7.7 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 @tamagui/elements have?

0 vulnerabilities are recorded for @tamagui/elements 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 @tamagui/elements vulnerabilities disclosed?

0 vulnerabilities were recorded for @tamagui/elements 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 @tamagui/elements 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 @tamagui/elements for upcoming vulnerabilities?

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