VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@nativescript-community/ui-label: vulnerability history, versions and safety

@nativescript-community/ui-label is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 117 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
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all @nativescript-community/ui-label vulnerabilities

Vulert verdict on @nativescript-community/ui-label 2.0.4 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @nativescript-community/ui-label is a malicious-package vulnerability — a published version contained hostile code rather than a bug. Do not install it, and check whether it is already resolved in your dependencies.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

The current release contains malicious code, which caps this score.

What to do: Do not install this package. If it is already in your dependency tree, remove or replace it, and check what resolved it in the first place. Vulert keeps watching the name: if a maintained replacement appears, you will see it here. Monitor it with Vulert →

  • Current release 2.0.4 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 16 Sep 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Stars 20 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 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 @nativescript-community/ui-label, 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.0.4 04 Sep 2026 C1 malicious Apache-2.0 No Details →
2.0.3 04 Sep 2026 C1 malicious Apache-2.0 No Details →
2.0.2 30 Aug 2026 C1 malicious Apache-2.0 No Details →
2.0.1 11 Aug 2026 C1 malicious Apache-2.0 No Details →
2.0.0 11 Jun 2026 C1 malicious Apache-2.0 No Details →
1.3.43 13 May 2026 C1 malicious Apache-2.0 No Details →
1.3.42 18 Feb 2026 C1 malicious Apache-2.0 No Details →
1.3.41 10 Oct 2025 C1 malicious Apache-2.0 No Details →
1.3.40 29 Sep 2025 C1 malicious Apache-2.0 No Details →
1.3.39 29 Sep 2025 C1 malicious Apache-2.0 No Details →
1.3.38 26 Sep 2025 C1 malicious Apache-2.0 No Details →
1.3.34 05 Sep 2025 C1 malicious Apache-2.0 No Details →
1.3.33 16 Dec 2024 C1 malicious Apache-2.0 No Details →
1.3.32 19 Sep 2024 C1 malicious Apache-2.0 No Details →
1.3.30 18 Sep 2024 C1 malicious Apache-2.0 No Details →
1.3.29 22 May 2024 C1 malicious Apache-2.0 No Details →
1.3.28 22 May 2024 C1 malicious Apache-2.0 No Details →
1.3.27 02 May 2024 C1 malicious Apache-2.0 No Details →
1.3.26 18 Mar 2024 C1 malicious Apache-2.0 No Details →
1.3.25 06 Mar 2024 C1 malicious Apache-2.0 No Details →
1.3.24 05 Mar 2024 C1 malicious Apache-2.0 No Details →
1.3.23 05 Mar 2024 C1 malicious Apache-2.0 No Details →
1.3.22 22 Feb 2024 C1 malicious Apache-2.0 No Details →
1.3.21 15 Feb 2024 C1 malicious Apache-2.0 No Details →
1.3.20 12 Feb 2024 C1 malicious Apache-2.0 No Details →
1.3.19 12 Feb 2024 C1 malicious Apache-2.0 No Details →
1.3.18 30 Jan 2024 C1 malicious Apache-2.0 No Details →
1.3.17 25 Jan 2024 C1 malicious Apache-2.0 No Details →
1.3.16 23 Jan 2024 C1 malicious Apache-2.0 No Details →
1.3.15 23 Jan 2024 C1 malicious Apache-2.0 No Details →
1.3.14 23 Jan 2024 C1 malicious Apache-2.0 No Details →
1.3.13 18 Jan 2024 C1 malicious Apache-2.0 No Details →
1.3.12 18 Jan 2024 C1 malicious Apache-2.0 No Details →
1.3.11 16 Jan 2024 C1 malicious Apache-2.0 No Details →
1.3.10 14 Jan 2024 C1 malicious Apache-2.0 No Details →
1.3.9 29 Dec 2023 C1 malicious Apache-2.0 No Details →
1.3.8 06 Sep 2023 C1 malicious Apache-2.0 No Details →
1.3.7 12 Aug 2023 C1 malicious Apache-2.0 No Details →
1.3.6 08 Jun 2023 C1 malicious Apache-2.0 No Details →
1.3.5 16 May 2023 C1 malicious Apache-2.0 No Details →
1.3.4 14 May 2023 C1 malicious Apache-2.0 No Details →
1.3.3 13 May 2023 C1 malicious Apache-2.0 No Details →
1.3.2 12 May 2023 C1 malicious Apache-2.0 No Details →
1.3.1 11 May 2023 C1 malicious Apache-2.0 No Details →
1.3.0 10 May 2023 C1 malicious Apache-2.0 No Details →
1.2.27 20 Apr 2023 C1 malicious Apache-2.0 No Details →
1.2.26 01 Apr 2023 C1 malicious Apache-2.0 No Details →
1.2.25 21 Mar 2023 C1 malicious Apache-2.0 No Details →
1.2.24 13 Mar 2023 C1 malicious Apache-2.0 No Details →
1.2.23 25 Feb 2023 C1 malicious Apache-2.0 No Details →
1.2.22 20 Feb 2023 C1 malicious Apache-2.0 No Details →
1.2.21 30 Jan 2023 C1 malicious Apache-2.0 No Details →
1.2.20 24 Jan 2023 C1 malicious Apache-2.0 No Details →
1.2.19 17 Jan 2023 C1 malicious Apache-2.0 No Details →
1.2.18 17 Jan 2023 C1 malicious Apache-2.0 No Details →
1.2.16 01 Dec 2022 C1 malicious Apache-2.0 No Details →
1.2.15 21 Nov 2022 C1 malicious Apache-2.0 No Details →
1.2.14 20 Nov 2022 C1 malicious Apache-2.0 No Details →
1.2.13 02 Nov 2022 C1 malicious Apache-2.0 No Details →
1.2.12 16 Sep 2022 C1 malicious Apache-2.0 No Details →
1.2.11 09 Sep 2022 C1 malicious Apache-2.0 No Details →
1.2.10 01 Sep 2022 C1 malicious Apache-2.0 No Details →
1.2.9 22 Jul 2022 C1 malicious Apache-2.0 No Details →
1.2.8 26 Apr 2022 C1 malicious Apache-2.0 No Details →
1.2.7 05 Apr 2022 C1 malicious Apache-2.0 No Details →
1.2.6 09 Feb 2022 C1 malicious Apache-2.0 No Details →
1.2.5 09 Feb 2022 C1 malicious Apache-2.0 No Details →
1.2.4 14 Jan 2022 C1 malicious Apache-2.0 No Details →
1.2.3 13 Jan 2022 C1 malicious Apache-2.0 No Details →
1.2.2 08 Jan 2022 C1 malicious Apache-2.0 No Details →
1.2.1 02 Jan 2022 C1 malicious Apache-2.0 No Details →
1.2.0 20 Oct 2021 C1 malicious Apache-2.0 No Details →
1.1.25 09 Aug 2021 C1 malicious Apache-2.0 No Details →
1.1.24 09 Aug 2021 C1 malicious Apache-2.0 No Details →
1.1.23 08 Aug 2021 C1 malicious Apache-2.0 No Details →
1.1.22 07 Aug 2021 C1 malicious Apache-2.0 No Details →
1.1.20 04 Aug 2021 C1 malicious Apache-2.0 No Details →
1.1.19 04 Aug 2021 C1 malicious Apache-2.0 No Details →
1.1.18 04 Aug 2021 C1 malicious Apache-2.0 No Details →
1.1.17 01 Jul 2021 C1 malicious Apache-2.0 No Details →
1.1.16 03 May 2021 C1 malicious Apache-2.0 No Details →
1.1.15 23 Apr 2021 C1 malicious Apache-2.0 No Details →
1.1.14 19 Apr 2021 C1 malicious Apache-2.0 No Details →
1.1.13 14 Apr 2021 C1 malicious Apache-2.0 No Details →
1.1.12 05 Apr 2021 C1 malicious Apache-2.0 No Details →
1.1.11 02 Apr 2021 C1 malicious Apache-2.0 No Details →
1.1.10 26 Mar 2021 C1 malicious Apache-2.0 No Details →
1.1.9 26 Mar 2021 C1 malicious Apache-2.0 No Details →
1.1.8 24 Mar 2021 C1 malicious Apache-2.0 No Details →
1.1.7 16 Mar 2021 C1 malicious Apache-2.0 No Details →
1.1.6 16 Mar 2021 C1 malicious Apache-2.0 No Details →
1.1.5 15 Mar 2021 C1 malicious Apache-2.0 No Details →
1.1.4 13 Mar 2021 C1 malicious Apache-2.0 No Details →
1.1.3 13 Mar 2021 C1 malicious Apache-2.0 No Details →
1.1.2 08 Mar 2021 C1 malicious Apache-2.0 No Details →
1.1.1 16 Feb 2021 C1 malicious Apache-2.0 No Details →
1.1.0 12 Feb 2021 C1 malicious Apache-2.0 No Details →
1.0.61 20 Dec 2020 C1 malicious Apache-2.0 No Details →
1.0.60 27 Nov 2020 C1 malicious Apache-2.0 No Details →
1.0.59 26 Nov 2020 C1 malicious Apache-2.0 No Details →
1.0.58 26 Nov 2020 C1 malicious — No Details →
1.0.57 23 Nov 2020 C1 malicious — No Details →
1.0.56 23 Nov 2020 C1 malicious — No Details →
1.0.55 22 Nov 2020 C1 malicious — No Details →
1.0.54 16 Nov 2020 C1 malicious — No Details →
1.0.53 29 Oct 2020 C1 malicious — No Details →
1.0.52 23 Oct 2020 C1 malicious — No Details →
1.0.51 23 Oct 2020 C1 malicious — No Details →
1.0.50 21 Oct 2020 C1 malicious — No Details →
1.0.49 11 Oct 2020 C1 malicious — No Details →
1.0.48 10 Oct 2020 C1 malicious — No Details →
1.0.47 08 Oct 2020 C1 malicious — No Details →
1.0.46 07 Oct 2020 C1 malicious — No Details →
1.0.45 08 Sep 2020 C1 malicious — No Details →
1.0.44 06 Sep 2020 C1 malicious — No Details →
1.0.43 07 Aug 2020 C1 malicious — No Details →
1.0.42 07 Aug 2020 C1 malicious — No Details →

All 117 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 @nativescript-community/ui-label

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Malicious Code Injection in @nativescript-community/ui-label: A Critical Security Threat N/A critical No fix published 16 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 @nativescript-community/ui-label

Is @nativescript-community/ui-label safe to use?

No. Vulert records a malicious-package vulnerability for @nativescript-community/ui-label: a published version contained hostile code rather than a bug, and the package looks like one that was withdrawn for abuse. Do not install it, and check whether it is already resolved in your dependencies.

What is @nativescript-community/ui-label's Vulert package health score?

Vulert scores @nativescript-community/ui-label 15/100, which reads as critical. 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 contains malicious code, which caps this score.

Is the latest version of @nativescript-community/ui-label affected?

Yes. 2.0.4, 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.

Which version of @nativescript-community/ui-label should I use?

2.0.4 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 @nativescript-community/ui-label have?

1 vulnerability is recorded for @nativescript-community/ui-label 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 @nativescript-community/ui-label vulnerabilities disclosed?

0 vulnerabilities were recorded for @nativescript-community/ui-label in the last 12 months, and the oldest entry in this database dates to 16 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 @nativescript-community/ui-label 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.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor @nativescript-community/ui-label for upcoming vulnerabilities?

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