Vulnerability Database · npm · Package report
@ledgerhq/live-env: vulnerability history, versions and safety
@ledgerhq/live-env is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @ledgerhq/live-env 4.1.0 i
Updated on 23 Oct 2026
Good news: 4.1.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Widely used
- Community Not enough data
What to do: Stay on 4.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 4.1.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 458 packages i
- Last release this month 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 @ledgerhq/live-env, 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.
- 4.1.0 24 Sep 2026
- 4.0.1-nightly.20260924020607 24 Sep 2026
- 4.0.1-nightly.20260923143315 23 Sep 2026
- 4.0.1-nightly.20260923074751 23 Sep 2026
- 4.0.1-nightly.20260923020451 23 Sep 2026
- 4.0.1-nightly.20260922020517 22 Sep 2026
- 4.0.1-nightly.20260919020457 19 Sep 2026
- 4.0.0-nightly.20260912020511 12 Sep 2026
- 4.0.0 11 Sep 2026
- 4.0.0-nightly.20260911020507 11 Sep 2026
- 4.0.0-nightly.20260910020512 10 Sep 2026
- 4.0.0-nightly.20260909020514 09 Sep 2026
- 4.0.0-nightly.20260908020515 08 Sep 2026
- 3.2.0 07 Sep 2026
- 4.0.0-nightly.20260905020452 05 Sep 2026
- 4.0.0-nightly.20260904020502 04 Sep 2026
- 3.2.0-nightly.20260903021109 03 Sep 2026
- 3.2.0-nightly.20260902021544 02 Sep 2026
- 3.2.0-nightly.20260901020738 01 Sep 2026
- 3.2.0-nightly.20260829020445 29 Aug 2026
- 3.1.0-nightly.20260828043625 28 Aug 2026
- 3.1.0 27 Aug 2026
- 3.1.0-nightly.20260827033858 27 Aug 2026
- 3.1.0-nightly.20260826023004 26 Aug 2026
- 3.1.0-nightly.20260825022546 25 Aug 2026
- 3.1.0-nightly.20260822022420 22 Aug 2026
- 3.1.0-nightly.20260821022924 21 Aug 2026
- 3.1.0-nightly.20260820022524 20 Aug 2026
- 3.0.0 04 Aug 2026
- 3.0.0-nightly.20260804030101 04 Aug 2026
- 3.0.0-nightly.20260801030117 01 Aug 2026
- 3.0.0-nightly.20260731121909 31 Jul 2026
- 3.0.0-nightly.20260731030119 31 Jul 2026
- 3.0.0-nightly.20260730030101 30 Jul 2026
- 3.0.0-nightly.20260729052430 29 Jul 2026
- 3.0.0-nightly.20260729030041 29 Jul 2026
- 2.42.0 23 Jul 2026
- 2.42.0-nightly.20260723030324 23 Jul 2026
- 2.42.0-nightly.20260722030527 22 Jul 2026
- 2.42.0-nightly.20260721152948 21 Jul 2026
- 2.42.0-nightly.20260721121314 21 Jul 2026
- 2.42.0-nightly.20260721030453 21 Jul 2026
- 2.41.0-nightly.20260718030452 18 Jul 2026
- 2.41.0-nightly.20260717030514 17 Jul 2026
- 2.41.0 16 Jul 2026
- 2.41.0-nightly.20260716030502 16 Jul 2026
- 2.40.1-nightly.20260715030507 15 Jul 2026
- 2.40.1-nightly.20260714030307 14 Jul 2026
- 2.40.1-nightly.20260711030526 11 Jul 2026
- 2.40.1-nightly.20260710083506 10 Jul 2026
- 2.40.1-nightly.20260710030609 10 Jul 2026
- 2.40.1-nightly.20260709093723 09 Jul 2026
- 2.40.1-nightly.20260709030615 09 Jul 2026
- 2.40.1-nightly.20260708030542 08 Jul 2026
- 2.40.1-nightly.20260707131816 07 Jul 2026
- 2.40.1-nightly.20260707030641 07 Jul 2026
- 2.40.1-nightly.20260706195120 06 Jul 2026
- 2.40.1-nightly.20260706190747 06 Jul 2026
- 2.40.1-nightly.20260706182010 06 Jul 2026
- 2.40.1-nightly.20260706161023 06 Jul 2026
- 2.40.1-nightly.20260706141300 06 Jul 2026
- 2.40.1-nightly.20260706132733 06 Jul 2026
- 2.40.1-nightly.20260706103435 06 Jul 2026
- 2.40.1-nightly.20260706100408 06 Jul 2026
- 2.40.1-nightly.20260706080103 06 Jul 2026
- 2.40.1-nightly.20260704030539 04 Jul 2026
- 2.40.0-nightly.20260702030619 02 Jul 2026
- 2.40.0-nightly.20260701071638 01 Jul 2026
- 2.40.0-nightly.20260701030711 01 Jul 2026
- 2.40.0 30 Jun 2026
- 2.40.0-nightly.20260630030734 30 Jun 2026
- 2.40.0-nightly.20260627030713 27 Jun 2026
- 2.40.0-nightly.20260626030713 26 Jun 2026
- 2.40.0-nightly.20260625030731 25 Jun 2026
- 2.40.0-nightly.20260624030532 24 Jun 2026
- 2.40.0-nightly.20260623030753 23 Jun 2026
- 2.39.0 22 Jun 2026
- 2.39.0-nightly.20260620030702 20 Jun 2026
- 2.39.0-nightly.20260619030847 19 Jun 2026
- 2.39.0-nightly.20260618030726 18 Jun 2026
- 2.39.0-nightly.20260617030824 17 Jun 2026
- 2.39.0-nightly.20260616030802 16 Jun 2026
- 2.39.0-nightly.20260613030736 13 Jun 2026
- 2.38.0-nightly.20260612030643 12 Jun 2026
- 2.38.0 11 Jun 2026
- 2.38.0-nightly.20260611030748 11 Jun 2026
- 2.38.0-nightly.20260610030722 10 Jun 2026
- 2.38.0-nightly.20260609030647 09 Jun 2026
- 2.38.0-nightly.20260606030643 06 Jun 2026
- 2.37.0 05 Jun 2026
- 2.37.0-nightly.20260605030615 05 Jun 2026
- 2.37.0-nightly.20260604030755 04 Jun 2026
- 2.37.0-nightly.20260603081117 03 Jun 2026
- 2.37.0-nightly.20260603030820 03 Jun 2026
- 2.37.0-nightly.20260602030710 02 Jun 2026
- 2.37.0-nightly.20260530030617 30 May 2026
- 2.37.0-nightly.20260529151329 29 May 2026
- 2.37.0-nightly.20260529145638 29 May 2026
- 2.36.0-nightly.20260529072926 29 May 2026
- 2.36.0-nightly.20260529030713 29 May 2026
- 2.36.0 28 May 2026
- 2.35.1-nightly.20260528030659 28 May 2026
- 2.35.1-nightly.20260527030754 27 May 2026
- 2.35.1-nightly.20260526030636 26 May 2026
- 2.35.1-nightly.20260523030637 23 May 2026
- 2.35.0-nightly.20260522030722 22 May 2026
- 2.35.0 21 May 2026
- 2.35.0-nightly.20260521030625 21 May 2026
- 2.35.0-nightly.20260520091357 20 May 2026
- 2.35.0-nightly.20260519030629 19 May 2026
- 2.35.0-nightly.20260516030537 16 May 2026
- 2.35.0-nightly.20260515030840 15 May 2026
- 2.34.1-nightly.20260514030705 14 May 2026
- 2.34.1-nightly.20260513161754 13 May 2026
- 2.34.0 13 May 2026
- 2.34.0-nightly.20260513030606 13 May 2026
- 2.34.0-nightly.20260512084337 12 May 2026
- 2.34.0-nightly.20260512030650 12 May 2026
- 2.34.0-nightly.20260509030614 09 May 2026
- 2.34.0-nightly.20260508030548 08 May 2026
The newest 120 of 453 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.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for @ledgerhq/live-env
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
Questions
About @ledgerhq/live-env
Is @ledgerhq/live-env safe to use?
Vulert has no vulnerabilities on record for @ledgerhq/live-env 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 @ledgerhq/live-env's Vulert package health score?
Vulert scores @ledgerhq/live-env 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 @ledgerhq/live-env affected?
No. 4.1.0, 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 @ledgerhq/live-env should I use?
4.1.0 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 @ledgerhq/live-env have?
0 vulnerabilities are recorded for @ledgerhq/live-env 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 @ledgerhq/live-env vulnerabilities disclosed?
0 vulnerabilities were recorded for @ledgerhq/live-env 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 @ledgerhq/live-env 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 @ledgerhq/live-env for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @ledgerhq/live-env version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.