VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

set-in: vulnerability history, versions and safety

set-in is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 7 releases, from Mar 2021 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 11 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all set-in vulnerabilities

Vulert verdict on set-in 2.0.5 i

Updated on 23 Oct 2026

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

Package health score 52/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 2.0.5 — unaffected i
  • Vulnerabilities on record 3 over 4 years · 1 in the last year i
  • Latest disclosure 11 Feb 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 4 i
  • OpenSSF scorecard 0/10 i
  • Last release 8 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 set-in, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.0.5 11 Feb 2026 none Apache-2.0 — Details →
2.0.4 21 Apr 2022 C1 Apache-2.0 Yes Details →
2.0.3 07 Mar 2022 C1 Apache-2.0 Yes Details →
2.0.1 23 Nov 2020 C2 Apache-2.0 Yes Details →
2.0.0 13 Jul 2016 C2 Apache-2.0 Yes Details →
1.1.1 20 Mar 2015 C2 ISC Yes Details →
1.1.0 20 Mar 2015 C2 ISC Yes Details →
1.0.0 29 Jan 2015 C2 ISC Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for set-in

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-25354: Prototype Pollution in set-in 9.8 critical 2.0.3 18 Mar 2022
CVE-2020-28273: Prototype Pollution in set-in 9.8 critical 2.0.1 19 Mar 2021
Critical Prototype Pollution Vulnerability in set-in Package 9.4 critical 2.0.5 11 Feb 2026

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 set-in

Is set-in safe to use?

Vulert records 3 vulnerabilities for set-in in npm: 3 critical, 0 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 set-in's Vulert package health score?

Vulert scores set-in 52/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 set-in affected?

No. 2.0.5, 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 set-in should I use?

2.0.5 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 set-in have?

3 vulnerabilities are recorded for set-in in the npm ecosystem: 3 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 set-in vulnerabilities disclosed?

1 vulnerability was recorded for set-in in the last 12 months, and the oldest entry in this database dates to 19 Mar 2021. 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 set-in 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 set-in for upcoming vulnerabilities?

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