Vulert records 1 vulnerabilities for ini in npm: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is ini's Vulert package health score?

Vulert scores ini 79/100, which reads as in good shape. 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 ini 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 ini 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 ini have?

1 vulnerability is recorded for ini in the npm ecosystem: 0 critical, 1 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 ini vulnerabilities disclosed?

0 vulnerabilities were recorded for ini in the last 12 months, and the oldest entry in this database dates to 10 Dec 2020. 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 ini 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 ini for upcoming vulnerabilities?

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

Vulnerability Database · npm · Package report

ini: vulnerability history, versions and safety

ini is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 15 releases, first recorded in Dec 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

1 vulnerabilities recorded H1

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 ini vulnerabilities

Vulert verdict on ini 7.0.0 i

Updated on 23 Oct 2026

Good news: 7.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 79/100

Security Minor issues
Maintenance Sustainable
Popularity Widely used
Community Quiet

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 1 over 1 year · 0 in the last year i
Latest disclosure 10 Dec 2020 i
Highest CVSS 7.3 i
With no published fix 0 i
Depended on by 3,807 packages i
Stars 821 i
OpenSSF scorecard 4/10 i
Last release 5 months ago i
Licence ISC i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 ini, 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
7.0.0	08 May 2026	none	ISC	—	Details →
6.0.0	22 Oct 2025	none	ISC	—	Details →
5.0.0	04 Sep 2024	none	ISC	—	Details →
4.1.3	22 May 2024	none	ISC	—	Details →
4.1.2	04 Mar 2024	none	ISC	—	Details →
4.1.1	16 May 2023	none	ISC	—	Details →
4.1.0	13 Apr 2023	none	ISC	—	Details →
4.0.0	21 Mar 2023	none	ISC	—	Details →
3.0.1	22 Aug 2022	none	ISC	—	Details →
3.0.0	05 Apr 2022	none	ISC	—	Details →
2.0.0	11 Dec 2020	none	ISC	—	Details →
1.3.8	11 Dec 2020	none	ISC	—	Details →
1.3.7	09 Dec 2020	none	ISC	—	Details →
1.3.6	08 Dec 2020	none	ISC	—	Details →
1.3.5	21 Nov 2017	H1	ISC	Yes	Details →
1.3.4	06 Jun 2015	H1	ISC	Yes	Details →
1.3.3	11 Feb 2015	H1	ISC	Yes	Details →
1.3.2	25 Nov 2014	H1	ISC	Yes	Details →
1.3.1	25 Nov 2014	H1	ISC	Yes	Details →
1.3.0	16 Sep 2014	H1	ISC	Yes	Details →
1.2.1	23 May 2014	H1	ISC	Yes	Details →
1.2.0	13 May 2014	H1	ISC	Yes	Details →
1.1.0	23 Jan 2013	H1	ISC	Yes	Details →
1.0.5	04 Oct 2012	H1	ISC	Yes	Details →
1.0.4	14 Aug 2012	H1	ISC	Yes	Details →
1.0.3	13 Aug 2012	H1	ISC	Yes	Details →
1.0.2	07 Jan 2012	H1	ISC	Yes	Details →
1.0.1	13 Sep 2011	H1	ISC	Yes	Details →
1.0.0	07 Aug 2011	H1	ISC	Yes	Details →

All 29 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

2020 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for ini

Vulnerability	Severity	Fixed version ↑	Disclosed ↑
CVE-2020-7788: Prototype Pollution in ini Package	7.3 high	1.3.6	10 Dec 2020

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