VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

foundation-sites: vulnerability history, versions and safety

foundation-sites is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 63 releases, first recorded in Oct 2024. 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 M1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 foundation-sites vulnerabilities

Vulert verdict on foundation-sites 6.9.0 i

Updated on 23 Oct 2026

Careful: 6.9.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.9.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 26 Oct 2024 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Depended on by 219 packages i
  • Stars 29,806 i
  • OpenSSF scorecard 2/10 i
  • Last release 24 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 foundation-sites, 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
6.9.0 27 Sep 2024 M1 MIT No Details →
6.8.1 18 Aug 2023 M1 MIT No Details →
6.8.0 18 Aug 2023 M1 MIT No Details →
6.7.5 12 Jul 2022 M1 MIT No Details →
6.7.4 02 Nov 2021 M1 MIT No Details →
6.7.3 27 Sep 2021 M1 MIT No Details →
6.7.2 09 Sep 2021 M1 MIT No Details →
6.7.1 01 Sep 2021 M1 MIT No Details →
6.7.0 30 Aug 2021 M1 MIT No Details →
6.6.3 08 Apr 2020 M1 MIT No Details →
6.6.2 30 Mar 2020 M1 MIT No Details →
6.6.1 13 Dec 2019 M1 MIT No Details →
6.6.0 05 Dec 2019 M1 MIT No Details →
6.5.3 27 Jan 2019 M1 MIT No Details →
6.5.2 23 Jan 2019 M1 MIT No Details →
6.5.1 15 Nov 2018 M1 MIT No Details →
6.5.0 30 Oct 2018 M1 MIT No Details →
6.5.0-rc.4 13 Oct 2018 M1 MIT No Details →
6.5.0-rc.3 13 Sep 2018 M1 MIT No Details →
6.5.0-rc.2 10 Jul 2018 M1 MIT No Details →
6.5.0-rc.1 25 Jun 2018 M1 MIT No Details →
6.4.4-rc1 04 Oct 2017 M1 MIT No Details →
6.4.3 18 Aug 2017 M1 MIT No Details →
6.4.2 10 Aug 2017 M1 MIT No Details →
6.4.2-rc2 02 Aug 2017 M1 MIT No Details →
6.4.2-rc1 25 Jul 2017 M1 MIT No Details →
6.4.1 30 Jun 2017 M1 MIT No Details →
6.4.0 27 Jun 2017 M1 MIT No Details →
6.4.0-rc5 22 Jun 2017 M1 MIT No Details →
6.4.0-rc4 19 Jun 2017 M1 MIT No Details →
6.4.0-rc3 09 Jun 2017 M1 MIT No Details →
6.4.0-rc2-1 03 Jun 2017 M1 MIT No Details →
6.4.0-rc1 01 Jun 2017 M1 MIT No Details →
6.3.1 28 Feb 2017 M1 MIT No Details →
6.3.1-rc1 04 Feb 2017 M1 MIT No Details →
6.3.0 15 Dec 2016 M1 MIT No Details →
6.3.0-rc3 09 Dec 2016 M1 MIT No Details →
6.3.0-rc2 07 Dec 2016 M1 MIT No Details →
6.3.0-rc1 01 Dec 2016 M1 MIT No Details →
6.2.4 21 Oct 2016 M1 MIT No Details →
6.2.4-rc2 14 Oct 2016 M1 MIT No Details →
6.2.4-rc1 07 Oct 2016 M1 MIT No Details →
6.2.3 27 May 2016 M1 MIT No Details →
6.2.2-0 27 May 2016 M1 MIT No Details →
6.2.2-rc2 20 May 2016 M1 MIT No Details →
6.2.2-rc1 11 May 2016 M1 MIT No Details →
6.2.1 08 Apr 2016 M1 MIT No Details →
6.2.0 26 Feb 2016 M1 MIT No Details →
6.2.0-rc.1 15 Feb 2016 M1 MIT No Details →
6.1.2 23 Jan 2016 M1 MIT No Details →
6.1.1 23 Dec 2015 M1 MIT No Details →
6.1.0 23 Dec 2015 M1 MIT No Details →
6.0.6 16 Dec 2015 M1 MIT No Details →
6.0.5 02 Dec 2015 M1 MIT No Details →
6.0.4 25 Nov 2015 M1 MIT No Details →
6.0.3 21 Nov 2015 M1 MIT No Details →
6.0.2 21 Nov 2015 M1 MIT No Details →
6.0.1 20 Nov 2015 M1 MIT No Details →
6.0.0 19 Nov 2015 M1 MIT No Details →
6.0.0-alpha.2 06 Nov 2015 M1 MIT No Details →
6.0.0-alpha.1 05 Nov 2015 M1 MIT No Details →
5.5.3 06 Oct 2015 M1 MIT No Details →
5.5.2 30 Apr 2015 M1 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 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 foundation-sites

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-26304: Foundation Regular Expression Denial of Service Vulnerability in foundation-sites 7.5 medium No fix published 26 Oct 2024

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 foundation-sites

Is foundation-sites safe to use?

Vulert records 1 vulnerabilities for foundation-sites in npm: 0 critical, 0 high, 1 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is foundation-sites's Vulert package health score?

Vulert scores foundation-sites 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of foundation-sites affected?

Yes. 6.9.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of foundation-sites should I use?

6.9.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 foundation-sites have?

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

0 vulnerabilities were recorded for foundation-sites in the last 12 months, and the oldest entry in this database dates to 26 Oct 2024. 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 foundation-sites 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 foundation-sites for upcoming vulnerabilities?

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