Vulnerability Database · npm · Package report
firefox-profile: vulnerability history, versions and safety
firefox-profile is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on firefox-profile 4.7.1 i
Updated on 23 Oct 2026
Good news: 4.7.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on 4.7.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.7.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 4.7.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 26 packages i
- Stars 60 i
- OpenSSF scorecard 3/10 i
- Last release 2 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 firefox-profile, 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.
- 4.7.1 03 Aug 2026
- 4.7.0 13 Aug 2024
- 4.6.0 15 Apr 2024
- 4.5.0 24 Dec 2023
- 4.4.0 28 Sep 2023
- 4.3.2 11 Apr 2023
- 4.2.2 01 Nov 2021
- 4.2.1 11 Sep 2021
- 4.2.0 10 Mar 2021
- 4.1.0 25 Feb 2021
- 4.0.0 21 Sep 2020
- 3.1.0-alpha.1 21 Sep 2020
- 2.0.0 13 Mar 2020
- 1.3.1 23 Feb 2020
- 1.3.0 18 Oct 2019
- 1.2.0 20 Aug 2018
- 1.1.0 28 Oct 2017
- 1.0.3 31 Jul 2017
- 1.0.2 20 Jun 2017
- 1.0.1 12 Jun 2017
- 1.0.0 11 Apr 2017
- 0.5.0 21 Mar 2017
- 0.4.9 03 Mar 2017
- 0.4.8 31 Jan 2017
- 0.4.7 11 Jan 2017
- 0.4.6 28 Dec 2016
- 0.4.5 12 Dec 2016
- 0.4.4 05 Dec 2016
- 0.4.3 10 Nov 2016
- 0.4.2 10 Sep 2016
- 0.4.1 05 Sep 2016
- 0.4.0 21 May 2016
- 0.3.13 23 Apr 2016
- 0.3.12 27 Mar 2016
- 0.3.11 09 Apr 2015
- 0.3.10 08 Apr 2015
- 0.3.9 10 Mar 2015
- 0.3.8 10 Mar 2015
- 0.3.7 25 Feb 2015
- 0.3.6 10 Nov 2014
- 0.3.5 06 Oct 2014
- 0.3.4 08 Sep 2014
- 0.3.3 11 Aug 2014
- 0.3.2 10 Aug 2014
- 0.3.1 09 Aug 2014
- 0.3.0 09 Aug 2014
- 0.2.12 02 Aug 2014
- 0.2.11 02 Aug 2014
- 0.2.10 13 Jul 2014
- 0.2.9 10 Jul 2014
- 0.2.7 28 Mar 2014
- 0.2.6 17 Feb 2014
- 0.2.5 09 Feb 2014
- 0.2.4 29 Jan 2014
- 0.2.3 16 Jan 2014
- 0.2.2 10 Jan 2014
- 0.2.1 29 Dec 2013
- 0.2.0 10 Dec 2013
- 0.1.4 25 Nov 2013
- 0.1.3 19 Nov 2013
- 0.1.2 07 Nov 2013
- 0.1.1 06 Nov 2013
- 0.0.3 23 Oct 2013
- 0.0.2 13 Oct 2013
- 0.0.1 08 Oct 2013
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 4.7.1 | 03 Aug 2026 | none | MIT | — | Details → |
| 4.7.0 | 13 Aug 2024 | none | MIT | — | Details → |
| 4.6.0 | 15 Apr 2024 | none | MIT | — | Details → |
| 4.5.0 | 24 Dec 2023 | none | MIT | — | Details → |
| 4.4.0 | 28 Sep 2023 | none | MIT | — | Details → |
| 4.3.2 | 11 Apr 2023 | none | MIT | — | Details → |
| 4.2.2 | 01 Nov 2021 | none | MIT | — | Details → |
| 4.2.1 | 11 Sep 2021 | none | MIT | — | Details → |
| 4.2.0 | 10 Mar 2021 | none | MIT | — | Details → |
| 4.1.0 | 25 Feb 2021 | none | MIT | — | Details → |
| 4.0.0 | 21 Sep 2020 | none | MIT | — | Details → |
| 3.1.0-alpha.1 | 21 Sep 2020 | none | MIT | — | Details → |
| 2.0.0 | 13 Mar 2020 | none | MIT | — | Details → |
| 1.3.1 | 23 Feb 2020 | none | MIT | — | Details → |
| 1.3.0 | 18 Oct 2019 | none | MIT | — | Details → |
| 1.2.0 | 20 Aug 2018 | none | MIT | — | Details → |
| 1.1.0 | 28 Oct 2017 | none | MIT | — | Details → |
| 1.0.3 | 31 Jul 2017 | none | MIT | — | Details → |
| 1.0.2 | 20 Jun 2017 | none | MIT | — | Details → |
| 1.0.1 | 12 Jun 2017 | none | MIT | — | Details → |
| 1.0.0 | 11 Apr 2017 | none | MIT | — | Details → |
| 0.5.0 | 21 Mar 2017 | none | MIT | — | Details → |
| 0.4.9 | 03 Mar 2017 | none | MIT | — | Details → |
| 0.4.8 | 31 Jan 2017 | none | MIT | — | Details → |
| 0.4.7 | 11 Jan 2017 | none | MIT | — | Details → |
| 0.4.6 | 28 Dec 2016 | none | MIT | — | Details → |
| 0.4.5 | 12 Dec 2016 | none | MIT | — | Details → |
| 0.4.4 | 05 Dec 2016 | none | MIT | — | Details → |
| 0.4.3 | 10 Nov 2016 | none | MIT | — | Details → |
| 0.4.2 | 10 Sep 2016 | none | MIT | — | Details → |
| 0.4.1 | 05 Sep 2016 | none | MIT | — | Details → |
| 0.4.0 | 21 May 2016 | none | MIT | — | Details → |
| 0.3.13 | 23 Apr 2016 | none | MIT | — | Details → |
| 0.3.12 | 27 Mar 2016 | none | MIT | — | Details → |
| 0.3.11 | 09 Apr 2015 | none | MIT | — | Details → |
| 0.3.10 | 08 Apr 2015 | none | MIT | — | Details → |
| 0.3.9 | 10 Mar 2015 | none | MIT | — | Details → |
| 0.3.8 | 10 Mar 2015 | none | MIT | — | Details → |
| 0.3.7 | 25 Feb 2015 | none | MIT | — | Details → |
| 0.3.6 | 10 Nov 2014 | none | MIT | — | Details → |
| 0.3.5 | 06 Oct 2014 | none | MIT | — | Details → |
| 0.3.4 | 08 Sep 2014 | none | MIT | — | Details → |
| 0.3.3 | 11 Aug 2014 | none | MIT | — | Details → |
| 0.3.2 | 10 Aug 2014 | none | MIT | — | Details → |
| 0.3.1 | 09 Aug 2014 | none | MIT | — | Details → |
| 0.3.0 | 09 Aug 2014 | none | MIT | — | Details → |
| 0.2.12 | 02 Aug 2014 | none | MIT | — | Details → |
| 0.2.11 | 02 Aug 2014 | none | MIT | — | Details → |
| 0.2.10 | 13 Jul 2014 | none | MIT | — | Details → |
| 0.2.9 | 10 Jul 2014 | none | MIT | — | Details → |
| 0.2.7 | 28 Mar 2014 | none | MIT | — | Details → |
| 0.2.6 | 17 Feb 2014 | none | MIT | — | Details → |
| 0.2.5 | 09 Feb 2014 | none | MIT | — | Details → |
| 0.2.4 | 29 Jan 2014 | none | MIT | — | Details → |
| 0.2.3 | 16 Jan 2014 | none | MIT | — | Details → |
| 0.2.2 | 10 Jan 2014 | none | MIT | — | Details → |
| 0.2.1 | 29 Dec 2013 | none | MIT | — | Details → |
| 0.2.0 | 10 Dec 2013 | none | MIT | — | Details → |
| 0.1.4 | 25 Nov 2013 | none | MIT | — | Details → |
| 0.1.3 | 19 Nov 2013 | none | MIT | — | Details → |
| 0.1.2 | 07 Nov 2013 | none | MIT | — | Details → |
| 0.1.1 | 06 Nov 2013 | none | MIT | — | Details → |
| 0.0.3 | 23 Oct 2013 | none | MIT | — | Details → |
| 0.0.2 | 13 Oct 2013 | none | MIT | — | Details → |
| 0.0.1 | 08 Oct 2013 | none | MIT | — | Details → |
All 65 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for firefox-profile
No vulnerabilities match this view.
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
Questions
About firefox-profile
Is firefox-profile safe to use?
Vulert has no vulnerabilities on record for firefox-profile in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is firefox-profile's Vulert package health score?
Vulert scores firefox-profile 74/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 firefox-profile affected?
No. 4.7.1, 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 firefox-profile should I use?
4.7.1 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 firefox-profile have?
0 vulnerabilities are recorded for firefox-profile in the npm ecosystem: 0 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 firefox-profile vulnerabilities disclosed?
0 vulnerabilities were recorded for firefox-profile in the last 12 months. 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 firefox-profile 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 firefox-profile for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the firefox-profile version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.