Vulnerability Database · npm · Package report

eslint-rule-docs: vulnerability history, versions and safety

Q: How do I monitor eslint-rule-docs for upcoming vulnerabilities?

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

eslint-rule-docs is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all eslint-rule-docs vulnerabilities

Vulert verdict on eslint-rule-docs 1.1.235 i

Updated on 23 Oct 2026

Good news: 1.1.235, the version you would install today, has no known vulnerabilities.

Package health score 51/100

Security Minor issues
Maintenance Unmaintained
Popularity Niche
Community Inactive

What to do: Stay on 1.1.235 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.1.235 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

Current release 1.1.235 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 1,070 packages i
Stars 9 i
OpenSSF scorecard 2/10 i
Last release 52 months ago i
Licence MIT 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for eslint-rule-docs, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
1.1.235	27 May 2022	none	MIT	—	Details →
1.1.234	27 May 2022	none	MIT	—	Details →
1.1.233	27 May 2022	none	MIT	—	Details →
1.1.232	27 May 2022	none	MIT	—	Details →
1.1.231	25 Jul 2021	none	MIT	—	Details →
1.1.230	04 Jul 2021	none	MIT	—	Details →
1.1.229	27 Jun 2021	none	MIT	—	Details →
1.1.228	20 Jun 2021	none	MIT	—	Details →
1.1.227	30 May 2021	none	MIT	—	Details →
1.1.226	02 May 2021	none	MIT	—	Details →
1.1.225	25 Apr 2021	none	MIT	—	Details →
1.1.224	11 Apr 2021	none	MIT	—	Details →
1.1.223	14 Mar 2021	none	MIT	—	Details →
1.1.222	21 Feb 2021	none	MIT	—	Details →
1.1.221	14 Feb 2021	none	MIT	—	Details →
1.1.220	07 Feb 2021	none	MIT	—	Details →
1.1.219	17 Jan 2021	none	MIT	—	Details →
1.1.218	03 Jan 2021	none	MIT	—	Details →
1.1.217	13 Dec 2020	none	MIT	—	Details →
1.1.216	06 Dec 2020	none	MIT	—	Details →
1.1.215	22 Nov 2020	none	MIT	—	Details →
1.1.214	08 Nov 2020	none	MIT	—	Details →
1.1.213	01 Nov 2020	none	MIT	—	Details →
1.1.212	18 Oct 2020	none	MIT	—	Details →
1.1.211	11 Oct 2020	none	MIT	—	Details →
1.1.210	04 Oct 2020	none	MIT	—	Details →
1.1.209	27 Sep 2020	none	MIT	—	Details →
1.1.208	06 Sep 2020	none	MIT	—	Details →
1.1.207	30 Aug 2020	none	MIT	—	Details →
1.1.206	26 Aug 2020	none	MIT	—	Details →
1.1.205	23 Aug 2020	none	MIT	—	Details →
1.1.204	16 Aug 2020	none	MIT	—	Details →
1.1.203	09 Aug 2020	none	MIT	—	Details →
1.1.202	02 Aug 2020	none	MIT	—	Details →
1.1.201	26 Jul 2020	none	MIT	—	Details →
1.1.200	19 Jul 2020	none	MIT	—	Details →
1.1.199	12 Jul 2020	none	MIT	—	Details →
1.1.198	05 Jul 2020	none	MIT	—	Details →
1.1.197	28 Jun 2020	none	MIT	—	Details →
1.1.196	21 Jun 2020	none	MIT	—	Details →
1.1.195	14 Jun 2020	none	MIT	—	Details →
1.1.194	07 Jun 2020	none	MIT	—	Details →
1.1.193	31 May 2020	none	MIT	—	Details →
1.1.192	24 May 2020	none	MIT	—	Details →
1.1.191	17 May 2020	none	MIT	—	Details →
1.1.190	10 May 2020	none	MIT	—	Details →
1.1.189	03 May 2020	none	MIT	—	Details →
1.1.188	26 Apr 2020	none	MIT	—	Details →
1.1.187	19 Apr 2020	none	MIT	—	Details →
1.1.186	12 Apr 2020	none	MIT	—	Details →
1.1.185	05 Apr 2020	none	MIT	—	Details →
1.1.184	29 Mar 2020	none	MIT	—	Details →
1.1.183	22 Mar 2020	none	MIT	—	Details →
1.1.182	15 Mar 2020	none	MIT	—	Details →
1.1.181	08 Mar 2020	none	MIT	—	Details →
1.1.180	01 Mar 2020	none	MIT	—	Details →
1.1.179	23 Feb 2020	none	MIT	—	Details →
1.1.178	16 Feb 2020	none	MIT	—	Details →
1.1.177	02 Feb 2020	none	MIT	—	Details →
1.1.176	26 Jan 2020	none	MIT	—	Details →
1.1.175	19 Jan 2020	none	MIT	—	Details →
1.1.174	12 Jan 2020	none	MIT	—	Details →
1.1.173	05 Jan 2020	none	MIT	—	Details →
1.1.172	29 Dec 2019	none	MIT	—	Details →
1.1.171	22 Dec 2019	none	MIT	—	Details →
1.1.170	15 Dec 2019	none	MIT	—	Details →
1.1.169	08 Dec 2019	none	MIT	—	Details →
1.1.168	01 Dec 2019	none	MIT	—	Details →
1.1.167	24 Nov 2019	none	MIT	—	Details →
1.1.166	17 Nov 2019	none	MIT	—	Details →
1.1.165	10 Nov 2019	none	MIT	—	Details →
1.1.164	03 Nov 2019	none	MIT	—	Details →
1.1.163	27 Oct 2019	none	MIT	—	Details →
1.1.162	20 Oct 2019	none	MIT	—	Details →
1.1.161	18 Oct 2019	none	MIT	—	Details →
1.1.160	18 Oct 2019	none	MIT	—	Details →
1.1.159	18 Oct 2019	none	MIT	—	Details →
1.1.158	18 Sep 2019	none	MIT	—	Details →
1.1.157	11 Aug 2019	none	MIT	—	Details →
1.1.156	09 Aug 2019	none	MIT	—	Details →
1.1.155	07 Aug 2019	none	MIT	—	Details →
1.1.154	31 Jul 2019	none	MIT	—	Details →
1.1.153	29 Jul 2019	none	MIT	—	Details →
1.1.152	25 Jul 2019	none	MIT	—	Details →
1.1.151	24 Jul 2019	none	MIT	—	Details →
1.1.150	22 Jul 2019	none	MIT	—	Details →
1.1.149	20 Jul 2019	none	MIT	—	Details →
1.1.148	19 Jul 2019	none	MIT	—	Details →
1.1.147	15 Jul 2019	none	MIT	—	Details →
1.1.146	13 Jul 2019	none	MIT	—	Details →
1.1.145	12 Jul 2019	none	MIT	—	Details →
1.1.144	10 Jul 2019	none	MIT	—	Details →
1.1.143	09 Jul 2019	none	MIT	—	Details →
1.1.142	07 Jul 2019	none	MIT	—	Details →
1.1.141	06 Jul 2019	none	MIT	—	Details →
1.1.140	03 Jul 2019	none	MIT	—	Details →
1.1.139	02 Jul 2019	none	MIT	—	Details →
1.1.138	28 Jun 2019	none	MIT	—	Details →
1.1.137	27 Jun 2019	none	MIT	—	Details →
1.1.136	26 Jun 2019	none	MIT	—	Details →
1.1.135	25 Jun 2019	none	—	—	Details →
1.1.134	21 Jun 2019	none	—	—	Details →
1.1.133	20 Jun 2019	none	—	—	Details →
1.1.132	19 Jun 2019	none	—	—	Details →
1.1.131	18 Jun 2019	none	—	—	Details →
1.1.130	17 Jun 2019	none	—	—	Details →
1.1.129	16 Jun 2019	none	—	—	Details →
1.1.128	14 Jun 2019	none	—	—	Details →
1.1.127	13 Jun 2019	none	—	—	Details →
1.1.126	11 Jun 2019	none	—	—	Details →
1.1.125	10 Jun 2019	none	—	—	Details →
1.1.124	08 Jun 2019	none	—	—	Details →
1.1.123	07 Jun 2019	none	—	—	Details →
1.1.122	06 Jun 2019	none	—	—	Details →
1.1.121	05 Jun 2019	none	—	—	Details →
1.1.120	04 Jun 2019	none	—	—	Details →
1.1.119	03 Jun 2019	none	—	—	Details →
1.1.118	31 May 2019	none	—	—	Details →
1.1.117	29 May 2019	none	—	—	Details →
1.1.116	28 May 2019	none	—	—	Details →

The newest 120 of 257 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 eslint-rule-docs

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

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 eslint-rule-docs

Is eslint-rule-docs safe to use?

Vulert has no vulnerabilities on record for eslint-rule-docs 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 eslint-rule-docs's Vulert package health score?

Vulert scores eslint-rule-docs 51/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 eslint-rule-docs affected?

No. 1.1.235, 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 eslint-rule-docs should I use?

1.1.235 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 eslint-rule-docs have?

0 vulnerabilities are recorded for eslint-rule-docs 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 eslint-rule-docs vulnerabilities disclosed?

0 vulnerabilities were recorded for eslint-rule-docs 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 eslint-rule-docs 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 eslint-rule-docs for upcoming vulnerabilities?

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