Vulnerability Database · npm · Package report
@semantic-release/commit-analyzer: vulnerability history, versions and safety
@semantic-release/commit-analyzer 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 @semantic-release/commit-analyzer 13.0.1 i
Updated on 23 Oct 2026
Good news: 13.0.1, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Maintaining
- Popularity Niche
- Community Quiet
What to do: Stay on 13.0.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 13.0.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 13.0.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 456 packages i
- Stars 446 i
- OpenSSF scorecard 6/10 i
- Last release 21 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 @semantic-release/commit-analyzer, 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.
- 14.0.0-beta.4 14 Sep 2026
- 14.0.0-beta.3 24 Aug 2026
- 14.0.0-beta.2 07 Aug 2026
- 14.0.0-beta.1 07 Aug 2026
- 13.0.1 03 Jan 2025
- 13.0.0 31 May 2024
- 13.0.0-beta.2 25 May 2024
- 13.0.0-beta.1 25 May 2024
- 12.0.0 18 Mar 2024
- 11.1.0 06 Nov 2023
- 11.0.0 18 Sep 2023
- 11.0.0-beta.4 17 Sep 2023
- 11.0.0-beta.3 15 Sep 2023
- 11.0.0-beta.2 12 Sep 2023
- 11.0.0-beta.1 01 Sep 2023
- 10.0.4 28 Aug 2023
- 10.0.3 28 Aug 2023
- 10.0.2 27 Aug 2023
- 10.0.1 07 Jun 2023
- 10.0.0 02 Jun 2023
- 10.0.0-beta.1 30 May 2023
- 9.0.2 23 Nov 2021
- 9.0.1 18 Sep 2021
- 9.0.0 17 Sep 2021
- 9.0.0-beta.3 03 Sep 2021
- 9.0.0-beta.2 21 Aug 2021
- 9.0.0-beta.1 20 Aug 2021
- 8.0.1 31 Jan 2020
- 8.0.0 27 Jan 2020
- 7.0.0 09 Jan 2020
- 7.0.0-beta.7 05 Dec 2019
- 7.0.0-beta.6 21 Nov 2019
- 7.0.0-beta.5 21 Nov 2019
- 6.3.3 07 Nov 2019
- 6.3.2 30 Oct 2019
- 6.3.1 26 Oct 2019
- 7.0.0-beta.4 02 Oct 2019
- 7.0.0-beta.3 21 Aug 2019
- 6.3.0 09 Aug 2019
- 6.2.0 07 Jun 2019
- 6.1.1 08 May 2019
- 7.0.0-beta.2 21 Mar 2019
- 7.0.0-beta.1 29 Nov 2018
- 6.1.0 08 Oct 2018
- 6.0.1 11 Sep 2018
- 6.0.0 17 Jul 2018
- 5.1.0 10 Jul 2018
- 5.0.5 06 Jun 2018
- 5.0.4 29 May 2018
- 5.0.3 22 Mar 2018
- 5.0.2 09 Feb 2018
- 5.0.1 21 Jan 2018
- 5.0.0 25 Nov 2017
- 4.0.1 22 Nov 2017
- 4.0.0 30 Oct 2017
- 3.0.7 10 Oct 2017
- 3.0.6 01 Oct 2017
- 3.0.5 01 Oct 2017
- 3.0.4 25 Sep 2017
- 3.0.3 21 Sep 2017
- 3.0.2 19 Sep 2017
- 3.0.1 18 Sep 2017
- 3.0.0 17 Sep 2017
- 2.0.0 19 Jul 2015
- 1.0.0 19 Jun 2015
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 14.0.0-beta.4 | 14 Sep 2026 | none | MIT | — | Details → |
| 14.0.0-beta.3 | 24 Aug 2026 | none | MIT | — | Details → |
| 14.0.0-beta.2 | 07 Aug 2026 | none | MIT | — | Details → |
| 14.0.0-beta.1 | 07 Aug 2026 | none | MIT | — | Details → |
| 13.0.1 | 03 Jan 2025 | none | MIT | — | Details → |
| 13.0.0 | 31 May 2024 | none | MIT | — | Details → |
| 13.0.0-beta.2 | 25 May 2024 | none | MIT | — | Details → |
| 13.0.0-beta.1 | 25 May 2024 | none | MIT | — | Details → |
| 12.0.0 | 18 Mar 2024 | none | MIT | — | Details → |
| 11.1.0 | 06 Nov 2023 | none | MIT | — | Details → |
| 11.0.0 | 18 Sep 2023 | none | MIT | — | Details → |
| 11.0.0-beta.4 | 17 Sep 2023 | none | MIT | — | Details → |
| 11.0.0-beta.3 | 15 Sep 2023 | none | MIT | — | Details → |
| 11.0.0-beta.2 | 12 Sep 2023 | none | MIT | — | Details → |
| 11.0.0-beta.1 | 01 Sep 2023 | none | MIT | — | Details → |
| 10.0.4 | 28 Aug 2023 | none | MIT | — | Details → |
| 10.0.3 | 28 Aug 2023 | none | MIT | — | Details → |
| 10.0.2 | 27 Aug 2023 | none | MIT | — | Details → |
| 10.0.1 | 07 Jun 2023 | none | MIT | — | Details → |
| 10.0.0 | 02 Jun 2023 | none | MIT | — | Details → |
| 10.0.0-beta.1 | 30 May 2023 | none | MIT | — | Details → |
| 9.0.2 | 23 Nov 2021 | none | MIT | — | Details → |
| 9.0.1 | 18 Sep 2021 | none | MIT | — | Details → |
| 9.0.0 | 17 Sep 2021 | none | MIT | — | Details → |
| 9.0.0-beta.3 | 03 Sep 2021 | none | MIT | — | Details → |
| 9.0.0-beta.2 | 21 Aug 2021 | none | MIT | — | Details → |
| 9.0.0-beta.1 | 20 Aug 2021 | none | MIT | — | Details → |
| 8.0.1 | 31 Jan 2020 | none | MIT | — | Details → |
| 8.0.0 | 27 Jan 2020 | none | MIT | — | Details → |
| 7.0.0 | 09 Jan 2020 | none | MIT | — | Details → |
| 7.0.0-beta.7 | 05 Dec 2019 | none | MIT | — | Details → |
| 7.0.0-beta.6 | 21 Nov 2019 | none | MIT | — | Details → |
| 7.0.0-beta.5 | 21 Nov 2019 | none | MIT | — | Details → |
| 6.3.3 | 07 Nov 2019 | none | MIT | — | Details → |
| 6.3.2 | 30 Oct 2019 | none | MIT | — | Details → |
| 6.3.1 | 26 Oct 2019 | none | MIT | — | Details → |
| 7.0.0-beta.4 | 02 Oct 2019 | none | MIT | — | Details → |
| 7.0.0-beta.3 | 21 Aug 2019 | none | MIT | — | Details → |
| 6.3.0 | 09 Aug 2019 | none | MIT | — | Details → |
| 6.2.0 | 07 Jun 2019 | none | MIT | — | Details → |
| 6.1.1 | 08 May 2019 | none | MIT | — | Details → |
| 7.0.0-beta.2 | 21 Mar 2019 | none | MIT | — | Details → |
| 7.0.0-beta.1 | 29 Nov 2018 | none | MIT | — | Details → |
| 6.1.0 | 08 Oct 2018 | none | MIT | — | Details → |
| 6.0.1 | 11 Sep 2018 | none | MIT | — | Details → |
| 6.0.0 | 17 Jul 2018 | none | MIT | — | Details → |
| 5.1.0 | 10 Jul 2018 | none | MIT | — | Details → |
| 5.0.5 | 06 Jun 2018 | none | MIT | — | Details → |
| 5.0.4 | 29 May 2018 | none | MIT | — | Details → |
| 5.0.3 | 22 Mar 2018 | none | MIT | — | Details → |
| 5.0.2 | 09 Feb 2018 | none | MIT | — | Details → |
| 5.0.1 | 21 Jan 2018 | none | MIT | — | Details → |
| 5.0.0 | 25 Nov 2017 | none | MIT | — | Details → |
| 4.0.1 | 22 Nov 2017 | none | MIT | — | Details → |
| 4.0.0 | 30 Oct 2017 | none | MIT | — | Details → |
| 3.0.7 | 10 Oct 2017 | none | MIT | — | Details → |
| 3.0.6 | 01 Oct 2017 | none | MIT | — | Details → |
| 3.0.5 | 01 Oct 2017 | none | MIT | — | Details → |
| 3.0.4 | 25 Sep 2017 | none | MIT | — | Details → |
| 3.0.3 | 21 Sep 2017 | none | MIT | — | Details → |
| 3.0.2 | 19 Sep 2017 | none | MIT | — | Details → |
| 3.0.1 | 18 Sep 2017 | none | MIT | — | Details → |
| 3.0.0 | 17 Sep 2017 | none | MIT | — | Details → |
| 2.0.0 | 19 Jul 2015 | none | MIT | — | Details → |
| 1.0.0 | 19 Jun 2015 | 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.
03 Vulnerabilities
Recorded vulnerabilities for @semantic-release/commit-analyzer
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 @semantic-release/commit-analyzer
Is @semantic-release/commit-analyzer safe to use?
Vulert has no vulnerabilities on record for @semantic-release/commit-analyzer 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 @semantic-release/commit-analyzer's Vulert package health score?
Vulert scores @semantic-release/commit-analyzer 73/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 @semantic-release/commit-analyzer affected?
No. 13.0.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 @semantic-release/commit-analyzer should I use?
13.0.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 @semantic-release/commit-analyzer have?
0 vulnerabilities are recorded for @semantic-release/commit-analyzer 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 @semantic-release/commit-analyzer vulnerabilities disclosed?
0 vulnerabilities were recorded for @semantic-release/commit-analyzer 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 @semantic-release/commit-analyzer 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 @semantic-release/commit-analyzer for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @semantic-release/commit-analyzer version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.