VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

dynamoose: vulnerability history, versions and safety

dynamoose is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 22 releases, first recorded in Feb 2021. 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 H1
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 dynamoose vulnerabilities

Vulert verdict on dynamoose 4.2.0 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 4.2.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 08 Feb 2021 i
  • Highest CVSS 7.2 i
  • With no published fix 0 i
  • Depended on by 25 packages i
  • Stars 2,250 i
  • OpenSSF scorecard 4/10 i
  • Last release 5 months ago i
  • Licence Unlicense 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 dynamoose, 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
4.2.0 05 May 2026 none Unlicense — Details →
4.1.5 11 Jan 2026 none Unlicense — Details →
4.0.4 06 Apr 2025 none Unlicense — Details →
4.0.3 30 Dec 2024 none Unlicense — Details →
4.0.2 12 Oct 2024 none Unlicense — Details →
4.0.1 21 Apr 2024 none Unlicense — Details →
4.0.0 31 Dec 2023 none Unlicense — Details →
3.3.0 31 Dec 2023 none Unlicense — Details →
3.2.1 14 Sep 2023 none Unlicense — Details →
3.2.0 16 Apr 2023 none Unlicense — Details →
3.1.0 04 Sep 2022 none Unlicense — Details →
3.0.3 02 Sep 2022 none Unlicense — Details →
2.8.8 02 Sep 2022 none Unlicense — Details →
3.0.2 25 Aug 2022 none Unlicense — Details →
3.0.1 25 Aug 2022 none Unlicense — Details →
3.0.0 17 Aug 2022 none Unlicense — Details →
2.8.7 17 Aug 2022 none Unlicense — Details →
3.0.0-beta.12 16 Aug 2022 none Unlicense — Details →
3.0.0-beta.11 14 Aug 2022 none Unlicense — Details →
3.0.0-beta.10 12 Aug 2022 none Unlicense — Details →
3.0.0-beta.9 11 Aug 2022 none Unlicense — Details →
3.0.0-beta.8 08 Aug 2022 none Unlicense — Details →
3.0.0-beta.6 20 Jul 2022 none Unlicense — Details →
2.8.6 20 Jul 2022 none Unlicense — Details →
3.0.0-beta.5 10 Jun 2022 none Unlicense — Details →
2.8.5 15 Jan 2022 none Unlicense — Details →
3.0.0-beta.1 15 Jan 2022 none Unlicense — Details →
2.8.4 14 Jan 2022 none Unlicense — Details →
3.0.0-alpha.9 14 Jan 2022 none Unlicense — Details →
3.0.0-alpha.8 07 Jan 2022 none Unlicense — Details →
3.0.0-alpha.7 22 Dec 2021 none Unlicense — Details →
3.0.0-alpha.6 11 Dec 2021 none Unlicense — Details →
3.0.0-alpha.5 05 Dec 2021 none Unlicense — Details →
2.8.3 28 Nov 2021 none Unlicense — Details →
3.0.0-alpha.4 22 Nov 2021 none Unlicense — Details →
2.8.2 21 Sep 2021 none Unlicense — Details →
3.0.0-alpha.3 22 Aug 2021 none Unlicense — Details →
2.8.1 21 Aug 2021 none Unlicense — Details →
2.8.0 14 Aug 2021 none Unlicense — Details →
3.0.0-alpha.2 21 Mar 2021 none Unlicense — Details →
2.7.3 17 Mar 2021 none Unlicense — Details →
2.7.2 14 Mar 2021 none Unlicense — Details →
3.0.0-alpha.1 13 Mar 2021 none Unlicense — Details →
2.7.1 11 Mar 2021 none Unlicense — Details →
2.7.0 06 Feb 2021 none Unlicense — Details →
2.6.0 31 Jan 2021 H1 Unlicense Yes Details →
2.5.0 13 Dec 2020 H1 Unlicense Yes Details →
2.4.1 26 Nov 2020 H1 Unlicense Yes Details →
2.4.0 22 Nov 2020 H1 Unlicense Yes Details →
2.3.0 28 Jul 2020 H1 Unlicense Yes Details →
2.3.0-beta.1 18 Jun 2020 H1 Unlicense Yes Details →
2.2.1 25 May 2020 H1 Unlicense Yes Details →
2.2.0 13 May 2020 H1 Unlicense Yes Details →
2.1.3 09 May 2020 H1 Unlicense Yes Details →
2.1.2 05 May 2020 H1 Unlicense Yes Details →
2.1.1 05 May 2020 H1 Unlicense Yes Details →
2.1.0 30 Apr 2020 H1 Unlicense Yes Details →
2.0.0 27 Apr 2020 H1 Unlicense Yes Details →
2.1.0-alpha.9 25 Apr 2020 H1 Unlicense Yes Details →
2.0.0-beta.12 25 Apr 2020 none Unlicense — Details →
2.1.0-alpha.8 19 Apr 2020 H1 Unlicense Yes Details →
2.0.0-beta.11 19 Apr 2020 none Unlicense — Details →
2.0.0-beta.10 16 Apr 2020 none Unlicense — Details →
2.1.0-alpha.7 11 Apr 2020 H1 Unlicense Yes Details →
2.1.0-alpha.6 11 Apr 2020 H1 Unlicense Yes Details →
2.1.0-alpha.5 09 Apr 2020 H1 Unlicense Yes Details →
2.1.0-alpha.4 08 Apr 2020 H1 Unlicense Yes Details →
2.1.0-alpha.3 08 Apr 2020 H1 Unlicense Yes Details →
2.1.0-alpha.2 08 Apr 2020 H1 Unlicense Yes Details →
2.0.0-beta.9 08 Apr 2020 none Unlicense — Details →
2.1.0-alpha.1 08 Apr 2020 H1 Unlicense Yes Details →
2.0.0-beta.8 06 Apr 2020 none Unlicense — Details →
2.0.0-beta.7 01 Apr 2020 none Unlicense — Details →
2.0.0-beta.6 22 Mar 2020 none Unlicense — Details →
2.0.0-beta.5 21 Mar 2020 none Unlicense — Details →
2.0.0-beta.4 17 Mar 2020 none Unlicense — Details →
2.0.0-beta.3 09 Mar 2020 none Unlicense — Details →
2.0.0-beta.2 20 Feb 2020 none Unlicense — Details →
2.0.0-beta.1 16 Feb 2020 none Unlicense — Details →
1.11.1 05 Sep 2019 none MIT — Details →
1.11.0 25 Aug 2019 none MIT — Details →
1.10.0 28 Jun 2019 none MIT — Details →
1.9.0 27 Jun 2019 none MIT — Details →
1.8.5 25 Jun 2019 none MIT — Details →
1.8.4 23 Jun 2019 none MIT — Details →
1.8.3 22 Jun 2019 none MIT — Details →
1.8.2 22 Jun 2019 none MIT — Details →
1.8.1 22 Jun 2019 none MIT — Details →
1.8.0 11 Jun 2019 none MIT — Details →
1.7.3 15 May 2019 none MIT — Details →
1.7.2 18 Mar 2019 none MIT — Details →
1.7.1 18 Mar 2019 none MIT — Details →
1.7.0 18 Mar 2019 none MIT — Details →
1.6.5 03 Mar 2019 none MIT — Details →
1.6.4 19 Feb 2019 none MIT — Details →
1.6.3 18 Feb 2019 none MIT — Details →
1.6.2 13 Feb 2019 none MIT — Details →
1.6.1 10 Feb 2019 none MIT — Details →
1.6.0 10 Feb 2019 none MIT — Details →
1.5.2 07 Feb 2019 none MIT — Details →
1.5.1 06 Feb 2019 none — — Details →
1.5.0 20 Jan 2019 none — — Details →
1.4.0 14 Jan 2019 none — — Details →
1.3.1 11 Jan 2019 none — — Details →
1.3.0 17 Dec 2018 none — — Details →
1.2.0 01 Dec 2018 none — — Details →
1.1.0 22 Oct 2018 none — — Details →
1.0.1 15 Oct 2018 none — — Details →
1.0.0 30 Sep 2018 none — — Details →
0.8.7 22 Mar 2018 none — — Details →
0.8.6 18 Oct 2017 none — — Details →
0.8.5 30 Aug 2017 none — — Details →
0.8.3 09 Jul 2017 none — — Details →
0.8.2 06 Jul 2017 none — — Details →
0.8.1 03 Jul 2017 none — — Details →
0.8.0 03 Jul 2017 none — — Details →
0.7.0 25 Oct 2016 none — — Details →
0.6.0 29 Jul 2016 none — — Details →
0.5.0 02 Jul 2016 none — — Details →
0.4.1 09 Sep 2015 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 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 dynamoose

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-21304: Prototype Pollution in Dynamoose 7.2 high 2.7.0 08 Feb 2021

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 dynamoose

Is dynamoose safe to use?

Vulert records 1 vulnerabilities for dynamoose 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 dynamoose's Vulert package health score?

Vulert scores dynamoose 77/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 dynamoose affected?

No. 4.2.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 dynamoose should I use?

4.2.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 dynamoose have?

1 vulnerability is recorded for dynamoose 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 dynamoose vulnerabilities disclosed?

0 vulnerabilities were recorded for dynamoose in the last 12 months, and the oldest entry in this database dates to 08 Feb 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 dynamoose 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 dynamoose for upcoming vulnerabilities?

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