Vulnerability Database · Go · Package report

github.com/ldez/gomoddirectives: vulnerability history, versions and safety

Q: How do I monitor github.com/ldez/gomoddirectives for upcoming vulnerabilities?

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

github.com/ldez/gomoddirectives is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/ldez/gomoddirectives vulnerabilities

Vulert verdict on github.com/ldez/gomoddirectives v0.10.0 i

Updated on 23 Oct 2026

Good news: v0.10.0, the version you would install today, has no known vulnerabilities.

Package health score 68/100

Security Minor issues
Maintenance Sustainable
Popularity Little adoption
Community Quiet

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

Current release v0.10.0 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 18 i
OpenSSF scorecard 4/10 i
Last release 1 month ago i
Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/ldez/gomoddirectives, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
v0.10.1-0.20261001220534-e55df72af8b0	01 Oct 2026	none	Apache-2.0	—	Details →
v0.10.0	16 Sep 2026	none	Apache-2.0	—	Details →
v0.9.0	03 Jun 2026	none	Apache-2.0	—	Details →
v0.8.0	04 Dec 2025	none	Apache-2.0	—	Details →
v0.7.1	23 Sep 2025	none	Apache-2.0	—	Details →
v0.7.0	08 Jun 2025	none	Apache-2.0	—	Details →
v0.6.2-0.20250428160124-2a31e5d7a92a	28 Apr 2025	none	Apache-2.0	—	Details →
v0.6.2-0.20250414141443-ab57f6529c81	14 Apr 2025	none	Apache-2.0	—	Details →
v0.6.1	16 Jan 2025	none	Apache-2.0	—	Details →
v0.6.0	03 Dec 2024	none	Apache-2.0	—	Details →
v0.5.1-0.20241202002354-0121ff58909a	02 Dec 2024	none	Apache-2.0	—	Details →
v0.5.0	02 Dec 2024	none	Apache-2.0	—	Details →
v0.4.2	30 Nov 2024	none	Apache-2.0	—	Details →
v0.4.1	30 Nov 2024	none	Apache-2.0	—	Details →
v0.4.0	30 Nov 2024	none	Apache-2.0	—	Details →
v0.3.0	30 Nov 2024	none	Apache-2.0	—	Details →
v0.0.0-20240325134238-7ed190152253	25 Mar 2024	none	Apache-2.0	—	Details →
v0.2.4	25 Mar 2024	none	Apache-2.0	—	Details →
v0.2.4-0.20240325134238-7ed190152253	25 Mar 2024	none	Apache-2.0	—	Details →
v0.2.4-0.20230625181848-21fb70d8557a	25 Jun 2023	none	Apache-2.0	—	Details →
v0.2.4-0.20221130230147-b04c4b949bd5	30 Nov 2022	none	Apache-2.0	—	Details →
v0.2.4-0.20221130230009-2e5181f55189	30 Nov 2022	none	Apache-2.0	—	Details →
v0.2.4-0.20220810222533-6b41746c76fb	10 Aug 2022	none	Apache-2.0	—	Details →
v0.2.4-0.20220425210459-112a3f63d834	25 Apr 2022	none	Apache-2.0	—	Details →
v0.2.3	25 Apr 2022	none	Apache-2.0	—	Details →
v0.2.3-0.20220425204158-3ce9a6500b55	25 Apr 2022	none	Apache-2.0	—	Details →
v0.2.3-0.20210716162555-82673faed925	16 Jul 2021	none	Apache-2.0	—	Details →
v0.2.2	14 Jul 2021	none	Apache-2.0	—	Details →
v0.2.2-0.20210529193820-44c49771319d	29 May 2021	none	Apache-2.0	—	Details →
v0.2.1	06 Mar 2021	none	Apache-2.0	—	Details →
v0.2.0	06 Mar 2021	none	Apache-2.0	—	Details →
v0.1.1-0.20210306003113-fa5713036b6f	06 Mar 2021	none	Apache-2.0	—	Details →
v0.1.0	05 Mar 2021	none	Apache-2.0	—	Details →

All 33 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 github.com/ldez/gomoddirectives

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

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 github.com/ldez/gomoddirectives

Is github.com/ldez/gomoddirectives safe to use?

Vulert has no vulnerabilities on record for github.com/ldez/gomoddirectives 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 github.com/ldez/gomoddirectives's Vulert package health score?

Vulert scores github.com/ldez/gomoddirectives 68/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 github.com/ldez/gomoddirectives affected?

No. v0.10.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 github.com/ldez/gomoddirectives should I use?

v0.10.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 github.com/ldez/gomoddirectives have?

0 vulnerabilities are recorded for github.com/ldez/gomoddirectives 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 github.com/ldez/gomoddirectives vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/ldez/gomoddirectives 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 github.com/ldez/gomoddirectives 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 github.com/ldez/gomoddirectives for upcoming vulnerabilities?

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