Vulnerability Database · npm · Package report
@ledgerhq/errors: vulnerability history, versions and safety
@ledgerhq/errors 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/errors 7.0.0 i
Updated on 23 Oct 2026
Good news: 7.0.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Widely used
- Community Moderate
What to do: Stay on 7.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 7.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 7.0.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 123 packages i
- Stars 623 i
- Last release 2 months 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 @ledgerhq/errors, 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.
- 7.0.0 04 Aug 2026
- 7.0.0-nightly.20260804030101 04 Aug 2026
- 7.0.0-nightly.20260801030117 01 Aug 2026
- 7.0.0-nightly.20260731121909 31 Jul 2026
- 7.0.0-nightly.20260731030119 31 Jul 2026
- 7.0.0-nightly.20260730030101 30 Jul 2026
- 7.0.0-nightly.20260729052430 29 Jul 2026
- 7.0.0-nightly.20260729030041 29 Jul 2026
- 7.0.0-nightly.20260728100612 28 Jul 2026
- 7.0.0-nightly.20260728030028 28 Jul 2026
- 7.0.0-nightly.20260725030056 25 Jul 2026
- 6.36.1-nightly.20260702030619 02 Jul 2026
- 6.36.1-nightly.20260701071638 01 Jul 2026
- 6.36.1-nightly.20260701030711 01 Jul 2026
- 6.37.0 30 Jun 2026
- 6.36.1-nightly.20260630030734 30 Jun 2026
- 6.36.1-nightly.20260627030713 27 Jun 2026
- 6.36.1-nightly.20260626030713 26 Jun 2026
- 6.36.1-nightly.20260625030731 25 Jun 2026
- 6.36.1-nightly.20260624030532 24 Jun 2026
- 6.36.1-nightly.20260623030753 23 Jun 2026
- 6.36.1-nightly.20260620030702 20 Jun 2026
- 6.36.0-nightly.20260612030643 12 Jun 2026
- 6.36.0 11 Jun 2026
- 6.36.0-nightly.20260611030748 11 Jun 2026
- 6.36.0-nightly.20260610030722 10 Jun 2026
- 6.36.0-nightly.20260609030647 09 Jun 2026
- 6.36.0-nightly.20260606030643 06 Jun 2026
- 6.35.0 13 May 2026
- 6.35.0-nightly.20260513030606 13 May 2026
- 6.35.0-nightly.20260512084337 12 May 2026
- 6.35.0-nightly.20260512030650 12 May 2026
- 6.35.0-nightly.20260509030614 09 May 2026
- 6.35.0-nightly.20260508030548 08 May 2026
- 6.35.0-nightly.20260507030645 07 May 2026
- 6.34.1 06 May 2026
- 6.35.0-nightly.20260506192049 06 May 2026
- 6.35.0-nightly.20260506181813 06 May 2026
- 6.35.0-nightly.20260506114501 06 May 2026
- 6.35.0-nightly.20260506112450 06 May 2026
- 6.35.0-nightly.20260506110559 06 May 2026
- 6.35.0-nightly.20260506030559 06 May 2026
- 6.35.0-nightly.20260505181800 05 May 2026
- 6.35.0-nightly.20260505145833 05 May 2026
- 6.35.0-nightly.20260505134028 05 May 2026
- 6.35.0-nightly.20260505030539 05 May 2026
- 6.34.0 22 Apr 2026
- 6.34.0-nightly.20260422030546 22 Apr 2026
- 6.34.0-nightly.20260421030533 21 Apr 2026
- 6.34.0-nightly.20260418030511 18 Apr 2026
- 6.34.0-nightly.20260417030535 17 Apr 2026
- 6.33.0-nightly.20260416030536 16 Apr 2026
- 6.33.0-nightly.20260415165444 15 Apr 2026
- 6.33.0 15 Apr 2026
- 6.33.0-nightly.20260415030445 15 Apr 2026
- 6.33.0-nightly.20260414030519 14 Apr 2026
- 6.33.0-nightly.20260411030455 11 Apr 2026
- 6.33.0-nightly.20260410030516 10 Apr 2026
- 6.33.0-nightly.20260409030454 09 Apr 2026
- 6.33.0-nightly.20260408030522 08 Apr 2026
- 6.33.0-nightly.20260407030452 07 Apr 2026
- 6.33.0-nightly.20260406162714 06 Apr 2026
- 6.33.0-nightly.20260404030214 04 Apr 2026
- 6.33.0-nightly.20260403030418 03 Apr 2026
- 6.33.0-nightly.20260402081627 02 Apr 2026
- 6.33.0-nightly.20260402030421 02 Apr 2026
- 6.33.0-nightly.20260401142436 01 Apr 2026
- 6.33.0-nightly.20260401141222 01 Apr 2026
- 6.33.0-nightly.20260401093636 01 Apr 2026
- 6.33.0-nightly.20260401081247 01 Apr 2026
- 6.33.0-nightly.20260401030542 01 Apr 2026
- 6.33.0-nightly.20260331122518 31 Mar 2026
- 6.33.0-nightly.20260331091649 31 Mar 2026
- 6.33.0-nightly.20260331030457 31 Mar 2026
- 6.32.0-nightly.20260327030425 27 Mar 2026
- 6.32.0 26 Mar 2026
- 6.32.0-nightly.20260326030424 26 Mar 2026
- 6.32.0-nightly.20260325070518 25 Mar 2026
- 6.32.0-nightly.20260325030350 25 Mar 2026
- 6.32.0-nightly.20260324030059 24 Mar 2026
- 6.32.0-nightly.20260321025644 21 Mar 2026
- 6.32.0-nightly.20260320093641 20 Mar 2026
- 6.32.0-nightly.20260320030028 20 Mar 2026
- 6.32.0-nightly.20260319030508 19 Mar 2026
- 6.31.0 18 Mar 2026
- 6.31.0-nightly.20260318094835 18 Mar 2026
- 6.31.0-nightly.20260318030401 18 Mar 2026
- 6.31.0-nightly.20260317030141 17 Mar 2026
- 6.31.0-nightly.20260314025831 14 Mar 2026
- 6.30.0-nightly.20260313030039 13 Mar 2026
- 6.30.0 12 Mar 2026
- 6.30.0-nightly.20260312030215 12 Mar 2026
- 6.30.0-nightly.20260311112418 11 Mar 2026
- 6.30.0-nightly.20260310103226 10 Mar 2026
- 6.30.0-nightly.20260310025916 10 Mar 2026
- 6.30.0-nightly.20260307025456 07 Mar 2026
- 6.30.0-nightly.20260306030049 06 Mar 2026
- 6.30.0-nightly.20260305030127 05 Mar 2026
- 6.30.0-nightly.20260304025924 04 Mar 2026
- 6.30.0-nightly.20260303030407 03 Mar 2026
- 6.30.0-nightly.20260302084023 02 Mar 2026
- 6.30.0-nightly.20260228025221 28 Feb 2026
- 6.29.0 19 Jan 2026
- 6.29.0-nightly.20260117023915 17 Jan 2026
- 6.29.0-nightly.20260116124336 16 Jan 2026
- 6.29.0-nightly.20260116024452 16 Jan 2026
- 6.28.0-nightly.20260115164241 15 Jan 2026
- 6.29.0-nightly.20260115024415 15 Jan 2026
- 6.29.0-nightly.20260114024814 14 Jan 2026
- 6.29.0-nightly.20260113172719 13 Jan 2026
- 6.29.0-nightly.20260113024349 13 Jan 2026
- 6.29.0-nightly.20260110024039 10 Jan 2026
- 6.29.0-nightly.20260109024422 09 Jan 2026
- 6.29.0-nightly.20260108024339 08 Jan 2026
- 6.29.0-nightly.20260107024347 07 Jan 2026
- 6.28.0-nightly.20260103023926 03 Jan 2026
- 6.28.0-nightly.20260102024414 02 Jan 2026
- 6.28.0-nightly.20260101025100 01 Jan 2026
- 6.28.0-nightly.20251231115616 31 Dec 2025
- 6.28.0-nightly.20251231024225 31 Dec 2025
The newest 120 of 405 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/errors
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/errors
Is @ledgerhq/errors safe to use?
Vulert has no vulnerabilities on record for @ledgerhq/errors 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/errors's Vulert package health score?
Vulert scores @ledgerhq/errors 91/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/errors affected?
No. 7.0.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/errors should I use?
7.0.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/errors have?
0 vulnerabilities are recorded for @ledgerhq/errors 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/errors vulnerabilities disclosed?
0 vulnerabilities were recorded for @ledgerhq/errors 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/errors 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/errors for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @ledgerhq/errors version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.