Vulnerability Database · Go · Package report
gitlab.com/digitalxero/go-conventional-commit: vulnerability history, versions and safety
gitlab.com/digitalxero/go-conventional-commit is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
See all gitlab.com/digitalxero/go-conventional-commit vulnerabilities
Vulert verdict on gitlab.com/digitalxero/go-conventional-commit v1.0.7 i
Updated on 23 Oct 2026
Good news: v1.0.7, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.0.7 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.7 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.7 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 2 i
- Last release 71 months ago i
- Licence MIT i
Version list, release dates, licence and dependants published by the Go module proxy, 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 gitlab.com/digitalxero/go-conventional-commit, 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.
- v1.0.8-0.20261016234801-93e10e31a0ae 16 Oct 2026
- v1.0.7 11 Nov 2020
- v1.0.7-0.20201111202330-34346e8a899b 11 Nov 2020
- v1.0.6 11 Nov 2020
- v1.0.5 11 Nov 2020
- v1.0.4 10 Nov 2020
- v1.0.3 10 Nov 2020
- v1.0.2 10 Nov 2020
- v1.0.1 16 Oct 2020
- v1.0.0 28 May 2020
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v1.0.8-0.20261016234801-93e10e31a0ae | 16 Oct 2026 | none | MIT | — | Details → |
| v1.0.7 | 11 Nov 2020 | none | MIT | — | Details → |
| v1.0.7-0.20201111202330-34346e8a899b | 11 Nov 2020 | none | MIT | — | Details → |
| v1.0.6 | 11 Nov 2020 | none | MIT | — | Details → |
| v1.0.5 | 11 Nov 2020 | none | MIT | — | Details → |
| v1.0.4 | 10 Nov 2020 | none | MIT | — | Details → |
| v1.0.3 | 10 Nov 2020 | none | — | — | Details → |
| v1.0.2 | 10 Nov 2020 | none | — | — | Details → |
| v1.0.1 | 16 Oct 2020 | none | — | — | Details → |
| v1.0.0 | 28 May 2020 | none | — | — | Details → |
All 10 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 gitlab.com/digitalxero/go-conventional-commit
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 gitlab.com/digitalxero/go-conventional-commit
Is gitlab.com/digitalxero/go-conventional-commit safe to use?
Vulert has no vulnerabilities on record for gitlab.com/digitalxero/go-conventional-commit in Go 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 gitlab.com/digitalxero/go-conventional-commit's Vulert package health score?
Vulert scores gitlab.com/digitalxero/go-conventional-commit 52/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).
Is the latest version of gitlab.com/digitalxero/go-conventional-commit affected?
No. v1.0.7, 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 gitlab.com/digitalxero/go-conventional-commit should I use?
v1.0.7 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 gitlab.com/digitalxero/go-conventional-commit have?
0 vulnerabilities are recorded for gitlab.com/digitalxero/go-conventional-commit in the Go 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 gitlab.com/digitalxero/go-conventional-commit vulnerabilities disclosed?
0 vulnerabilities were recorded for gitlab.com/digitalxero/go-conventional-commit 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 gitlab.com/digitalxero/go-conventional-commit 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 gitlab.com/digitalxero/go-conventional-commit for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the gitlab.com/digitalxero/go-conventional-commit version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.