VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

seneca: vulnerability history, versions and safety

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

i
1 vulnerabilities recorded L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all seneca vulnerabilities

Vulert verdict on seneca 3.38.0 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

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

  • Current release 3.38.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 11 Sep 2019 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 121 packages i
  • Stars 3,957 i
  • OpenSSF scorecard 3/10 i
  • Last release 20 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.

01 Versions

Which versions are affected

Every version Vulert tracks for seneca, 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
3.38.0 07 Feb 2025 none MIT — Details →
4.0.0-rc5 07 Feb 2025 none MIT — Details →
4.0.0-rc4 12 Jul 2024 none MIT — Details →
3.37.2 12 Jul 2024 none MIT — Details →
4.0.0-rc3 11 Jul 2024 none MIT — Details →
3.37.1 11 Jul 2024 none MIT — Details →
3.37.0 10 Jun 2024 none MIT — Details →
4.0.0-rc2 06 Jun 2024 none MIT — Details →
4.0.0-rc.2 06 Jun 2024 none MIT — Details →
3.36.0 03 May 2024 none MIT — Details →
3.35.3 26 Apr 2024 none MIT — Details →
3.35.2 06 Mar 2024 none MIT — Details →
3.34.1 19 Jan 2024 none MIT — Details →
3.34.0 18 Jan 2024 none MIT — Details →
3.33.0 05 Nov 2023 none MIT — Details →
3.32.1 16 Sep 2023 none MIT — Details →
3.32.0 29 Jun 2023 none MIT — Details →
3.31.2 29 Jun 2023 none MIT — Details →
3.31.1 29 Jun 2023 none MIT — Details →
3.31.0 29 Jun 2023 none MIT — Details →
3.30.1 31 May 2023 none MIT — Details →
3.30.0 10 Feb 2023 none MIT — Details →
3.29.0 01 Sep 2022 none MIT — Details →
3.28.2 20 Jun 2022 none MIT — Details →
3.28.0 23 May 2022 none MIT — Details →
3.27.2 20 May 2022 none MIT — Details →
3.27.1 14 May 2022 none MIT — Details →
3.27.0 12 May 2022 none MIT — Details →
3.26.2 18 Apr 2022 none MIT — Details →
3.26.1 18 Apr 2022 none MIT — Details →
3.26.0 08 Apr 2022 none MIT — Details →
3.25.0 03 Nov 2021 none MIT — Details →
3.24.1 12 Oct 2021 none MIT — Details →
3.24.0 14 Sep 2021 none MIT — Details →
3.23.3 19 Apr 2021 none MIT — Details →
3.23.2 14 Jan 2021 none MIT — Details →
3.23.1 10 Dec 2020 none MIT — Details →
3.23.0 30 Nov 2020 none MIT — Details →
3.22.0 02 Jul 2020 none MIT — Details →
3.21.2 26 May 2020 none MIT — Details →
3.21.1 26 May 2020 none MIT — Details →
3.21.0 18 May 2020 none MIT — Details →
3.20.6 14 May 2020 none MIT — Details →
3.20.5 11 May 2020 none MIT — Details →
3.20.4 11 May 2020 none MIT — Details →
3.20.3 30 Mar 2020 none MIT — Details →
3.20.2 12 Mar 2020 none MIT — Details →
3.20.1 29 Jan 2020 none MIT — Details →
3.20.0 28 Jan 2020 none MIT — Details →
3.19.0 28 Jan 2020 none MIT — Details →
3.18.0 16 Jan 2020 none MIT — Details →
3.17.0 02 Oct 2019 none MIT — Details →
3.16.1 30 Sep 2019 none MIT — Details →
3.16.0 20 Sep 2019 none MIT — Details →
3.15.4 20 Sep 2019 none MIT — Details →
3.15.3 20 Sep 2019 none MIT — Details →
3.15.2 19 Sep 2019 none MIT — Details →
3.15.1 09 Sep 2019 none MIT — Details →
3.14.1 04 Sep 2019 none MIT — Details →
3.14.0 02 Sep 2019 none MIT — Details →
3.13.3 14 Aug 2019 none MIT — Details →
3.13.2 09 Aug 2019 none MIT — Details →
3.13.1 07 Aug 2019 none MIT — Details →
3.13.0 31 Jul 2019 none MIT — Details →
3.12.1 26 Jul 2019 none MIT — Details →
3.12.0 22 Jul 2019 none MIT — Details →
3.11.0 14 May 2019 none MIT — Details →
3.10.0 12 May 2019 none MIT — Details →
3.9.0 06 May 2019 none MIT — Details →
3.8.4 03 Mar 2019 L1 MIT Yes Details →
3.8.3 25 Feb 2019 L1 MIT Yes Details →
3.8.2 17 Feb 2019 L1 MIT Yes Details →
3.8.1 10 Feb 2019 L1 MIT Yes Details →
3.8.0 13 Jan 2019 L1 MIT Yes Details →
3.8.0-rc3 23 Dec 2018 L1 MIT Yes Details →
3.7.0 18 Jul 2018 L1 MIT Yes Details →
3.6.0 28 May 2018 L1 MIT Yes Details →
3.5.0 14 May 2018 L1 MIT Yes Details →
3.4.3 14 Oct 2017 L1 MIT Yes Details →
3.4.2 10 Aug 2017 L1 MIT Yes Details →
3.4.1 06 Jul 2017 L1 MIT Yes Details →
3.4.0 03 Jul 2017 L1 MIT Yes Details →
3.4.0-rc0 16 Jun 2017 L1 MIT Yes Details →
3.3.0 07 Feb 2017 L1 MIT Yes Details →
3.2.2 25 Oct 2016 L1 MIT Yes Details →
3.2.1 27 Sep 2016 L1 MIT Yes Details →
3.2.0 27 Sep 2016 L1 MIT Yes Details →
3.1.0 16 Sep 2016 L1 MIT Yes Details →
3.0.0 26 Aug 2016 L1 MIT Yes Details →
2.1.0 20 May 2016 L1 MIT Yes Details →
2.0.1 13 Apr 2016 L1 MIT Yes Details →
2.0.0 22 Mar 2016 L1 MIT Yes Details →
1.4.0 16 Mar 2016 L1 MIT Yes Details →
1.3.0 01 Mar 2016 L1 MIT Yes Details →
1.2.0 17 Feb 2016 L1 MIT Yes Details →
1.1.0 04 Feb 2016 L1 MIT Yes Details →
1.0.0 11 Jan 2016 L1 MIT Yes Details →
0.9.3 21 Dec 2015 L1 MIT Yes Details →
0.9.2 14 Dec 2015 L1 MIT Yes Details →
0.9.1 08 Dec 2015 L1 MIT Yes Details →
0.9.0 03 Dec 2015 L1 — Yes Details →
0.8.0 19 Nov 2015 L1 — Yes Details →
0.7.2 27 Oct 2015 L1 — Yes Details →
0.7.1 05 Oct 2015 L1 — Yes Details →
0.7.0 04 Oct 2015 L1 — Yes Details →
0.6.5 04 Sep 2015 L1 — Yes Details →
0.6.4 29 Jul 2015 L1 — Yes Details →
0.6.3 12 Jul 2015 L1 — Yes Details →
0.6.2 22 Jun 2015 L1 — Yes Details →
0.6.1 04 Feb 2015 L1 — Yes Details →
0.6.1-rc2 02 Feb 2015 L1 — Yes Details →
0.6.1-rc1 30 Jan 2015 L1 — Yes Details →
0.6.1-rc0 29 Jan 2015 L1 — Yes Details →
0.6.0-rc2 29 Jan 2015 L1 — Yes Details →
0.6.0 26 Jan 2015 L1 — Yes Details →
0.5.21 07 Oct 2014 L1 — Yes Details →
0.5.20 07 Sep 2014 L1 — Yes Details →
0.5.19 13 Jul 2014 L1 — Yes Details →
0.5.18 09 Jul 2014 L1 — Yes Details →
0.5.17 10 Apr 2014 L1 — Yes Details →

The newest 120 of 142 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 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.

03 Vulnerabilities

Recorded vulnerabilities for seneca

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-5483: Sensitive Data Exposure in seneca N/A low 3.9.0 11 Sep 2019

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 seneca

Is seneca safe to use?

Vulert records 1 vulnerabilities for seneca in npm: 0 critical, 0 high, 0 medium and 1 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 seneca's Vulert package health score?

Vulert scores seneca 76/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 seneca affected?

No. 3.38.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 seneca should I use?

3.38.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 seneca have?

1 vulnerability is recorded for seneca in the npm ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new seneca vulnerabilities disclosed?

0 vulnerabilities were recorded for seneca in the last 12 months, and the oldest entry in this database dates to 11 Sep 2019. 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 seneca 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 seneca for upcoming vulnerabilities?

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