Vulnerability Database · npm · Package report
typed-error: vulnerability history, versions and safety
typed-error 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 typed-error 3.2.3 i
Updated on 23 Oct 2026
Good news: 3.2.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Inactive
What to do: Stay on 3.2.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.2.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 3.2.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 525 packages i
- Stars 5 i
- OpenSSF scorecard 3/10 i
- Last release 7 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 typed-error, 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.
- 3.2.3 12 Mar 2026
- 3.2.3-build-add-npm-oidc-permissions-8cc1f47dac7fc4c8d5f04a97b7b929e12ac1ee51-1 12 Mar 2026
- 3.2.2 20 Apr 2023
- 3.2.2-build-flowzonify-8b3f4191d9ff1f27ee2c2d56cfc23cdc5d823fdc-1 20 Apr 2023
- 3.2.2-build-flowzonify-3cea469cefb40a91f064cc5d0e276f8edd194ec3-1 18 Apr 2023
- 3.2.2-dfunckt-patch-1-eb2bc57e4a168080b3dcb6c7325abec18e76c2ae 19 Nov 2021
- 3.2.2-dfunckt-patch-1-e0f2737daa9e15f16d9dd782960a86339bbb4a08 01 Jul 2021
- 3.2.1 05 Aug 2020
- 3.2.1-update-deps-2a76155592b8a72796f0f6bb94920253d4dd8656 05 Aug 2020
- 3.2.1-update-deps-dc41949015399154efb4529183daa0dfc9269b52 04 Aug 2020
- 3.2.0 20 Nov 2019
- 3.2.0-node12-22f293afc187e67b88dab280951eb6e2bb504b24 20 Nov 2019
- 4.0.0-node12-dfce0e7655d7f6b1120ac3267d23cc2f31d185d1 20 Nov 2019
- 4.0.0-node12-9667b15bf4a848189f18a5afbf0a68c6b6176620 19 Nov 2019
- 3.1.0 01 Apr 2019
- 3.1.0-maintenance-47c07a641fa39ddb833b41aff7a918accad08289 01 Apr 2019
- 3.1.0-maintenance-7d534e5dffd78cf69bc1b6fab692f278295fe0b3 14 Mar 2019
- 3.1.0-maintenance-8fcfb421a7b81d67fdd0aab93faa5ae5ae2ac93d 14 Mar 2019
- 3.0.3-maintenance-05054333f3b83b3a1a13693faa0126a95d693ace 14 Mar 2019
- 3.0.2 01 Nov 2018
- 3.0.2-CameronDiver-patch-1-aaa9391dc463c1037f85e845d30f6f9434bb4dc1 01 Nov 2018
- 3.0.1 29 Oct 2018
- 3.0.1-updates-94adac5d747f16b9228b39e56007ee0126c6f99c 29 Oct 2018
- 3.0.1-updates-4b16d26d9d278f83f49d0f6674bcefad283378ac 29 Oct 2018
- 3.0.1-updates-9666bcd609ac07662fe099183df328acc37d0b67 29 Oct 2018
- 1.0.1-updates-f9e1bdb8061c7deb07201a16c7797dd73c292f65 29 Oct 2018
- 3.0.0 17 Apr 2018
- 2.0.0 25 Jul 2017
- 1.1.1 25 Jul 2017
- 1.1.0 21 Jul 2017
- 1.0.1 22 May 2017
- 1.0.0 17 May 2017
- 0.1.0 12 Aug 2014
All 33 versions Vulert tracks for this package. 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 typed-error
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 typed-error
Is typed-error safe to use?
Vulert has no vulnerabilities on record for typed-error 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 typed-error's Vulert package health score?
Vulert scores typed-error 68/100, which reads as usable, but worth attention. 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 typed-error affected?
No. 3.2.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.
Which version of typed-error should I use?
3.2.3 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 typed-error have?
0 vulnerabilities are recorded for typed-error 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 typed-error vulnerabilities disclosed?
0 vulnerabilities were recorded for typed-error 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 typed-error 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 typed-error for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the typed-error version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.