Vulnerability Database · npm · Package report
extract-opts: vulnerability history, versions and safety
extract-opts 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 extract-opts 5.9.0 i
Updated on 23 Oct 2026
Good news: 5.9.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on 5.9.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 5.9.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 5.9.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 43 packages i
- Stars 7 i
- OpenSSF scorecard 3/10 i
- Last release 33 months ago i
- Licence Artistic-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 extract-opts, 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.
- 5.9.0-next.1704166718.5bd0f119cd9a664e5e7424e155a561d720e12151 02 Jan 2024
- 5.9.0 02 Jan 2024
- 5.8.0-next.1703831852.0f53e729d2f0ef0391a7e2241d5b3554c38d2d42 29 Dec 2023
- 5.8.0 29 Dec 2023
- 5.7.0-next.1703780663.333a8b3a3dade1b5fe6eb418376bb4631456e319 28 Dec 2023
- 5.7.0 28 Dec 2023
- 5.6.0 27 Dec 2023
- 5.6.0-next.1703664900.44a63877e208b45a2ce523406ae291905a938a7e 27 Dec 2023
- 5.5.0-next.1701793904.7caa0a307aa16d8b2c1224a87aeedc77cd25b843 05 Dec 2023
- 5.5.0 05 Dec 2023
- 5.4.1 05 Dec 2023
- 5.4.1-next.1701782418.5381e879a9d6452dc7ddd3e7dbb929ffb817a6ca 05 Dec 2023
- 5.4.0-next.1700839953.08f98e6531b14e213278591f1e22a8639187faed 24 Nov 2023
- 5.4.0 24 Nov 2023
- 5.3.0 21 Nov 2023
- 5.3.0-next.1700543634.b359719a87658aa052b2ec820d0f3f77550907cf 21 Nov 2023
- 5.2.0-next.1699978532.f314f4d82abe279471515de91ca4486a0b935a00 14 Nov 2023
- 5.2.0 14 Nov 2023
- 5.1.0-next.1699876894.6cec1f9f0fac1ede06b63b9c19eafb17fe657411 13 Nov 2023
- 5.1.0 13 Nov 2023
- 5.0.0-next.1699829970.6d2f92b55d986b61055f7df0cbc1c597bb5278cf 12 Nov 2023
- 5.0.0 12 Nov 2023
- 4.3.0-next.1575880873.fd190477a5f30c8517ff89b49ad5b2e74ffcb812 09 Dec 2019
- 4.3.0 09 Dec 2019
- 4.2.0 01 Dec 2019
- 4.2.0-next.1575171153.743d8176883deec82307aeba7026073241aa62a2 01 Dec 2019
- 4.1.0-next.1575147896.bb0ab7cdda585834d7ecf8f60a010bd4d873a4ea 30 Nov 2019
- 4.1.0 30 Nov 2019
- 4.1.0-next.1575147230.db6ad70e775308ad833bdaaf561dcbffeba7581d 30 Nov 2019
- 4.0.0-next.1574660357.da69c777fc96775a1b7563ece70baed7cd5fadd1 25 Nov 2019
- 4.0.0-next.1574656381.940571fb802b734414b77516ab96a3724971b0fe 25 Nov 2019
- 4.0.0 18 Nov 2019
- 4.0.0-next.1574048582.9b70d87f2dc565aa977f0c56099474b49fa13eed 18 Nov 2019
- 3.4.0-next.1573738703.9b68cedee47761550ae2b220938637083933f68e 14 Nov 2019
- 3.4.0-next.1573687647.64c1ed5a1326b8a4cdd828e478dc28e081765777 13 Nov 2019
- 3.4.0 13 Nov 2019
- 3.4.0-next.1573610226.be6ba5f1d865d3d547350fe3f379251792936ed8 13 Nov 2019
- 3.3.1 27 May 2016
- 3.3.0 27 May 2016
- 3.2.0 15 Jan 2016
- 3.1.0 14 Jan 2016
- 3.0.1 13 Mar 2015
- 3.0.0 13 Mar 2015
- 2.2.0 24 Jun 2013
- 2.0.0 23 Jun 2013
All 45 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 extract-opts
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 extract-opts
Is extract-opts safe to use?
Vulert has no vulnerabilities on record for extract-opts 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 extract-opts's Vulert package health score?
Vulert scores extract-opts 55/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 extract-opts affected?
No. 5.9.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 extract-opts should I use?
5.9.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 extract-opts have?
0 vulnerabilities are recorded for extract-opts 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 extract-opts vulnerabilities disclosed?
0 vulnerabilities were recorded for extract-opts 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 extract-opts 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 extract-opts for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the extract-opts version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.