Vulnerability Database · Go · Package report

github.com/ashanbrown/forbidigo: vulnerability history, versions and safety

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

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

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.

Vulert verdict on github.com/ashanbrown/forbidigo v1.6.0 i

Updated on 23 Oct 2026

Good news: v1.6.0, the version you would install today, has no known vulnerabilities.

Package health score 55/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

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

  • Current release v1.6.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 184 i
  • OpenSSF scorecard 2/10 i
  • Last release 39 months ago i
  • Licence Apache-2.0 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 github.com/ashanbrown/forbidigo, 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
v1.6.1-0.20241126013225-e4c2790f18c1 26 Nov 2024 none Apache-2.0 — Details →
v1.6.1-0.20240623181225-1b32d2f40b72 23 Jun 2024 none Apache-2.0 — Details →
v1.6.1-0.20231111222827-57bf5a72a4f5 11 Nov 2023 none Apache-2.0 — Details →
v1.5.5-0.20230704143044-ab8eef62315f 04 Jul 2023 none Apache-2.0 — Details →
v1.6.0 04 Jul 2023 none Apache-2.0 — Details →
v1.5.4 03 Jul 2023 none Apache-2.0 — Details →
v1.5.4-0.20230703020201-f6adf999270f 03 Jul 2023 none Apache-2.0 — Details →
v1.5.3 11 Jun 2023 none Apache-2.0 — Details →
v1.5.3-0.20230611181159-c506b285d7c2 11 Jun 2023 none Apache-2.0 — Details →
v1.5.2 11 Jun 2023 none Apache-2.0 — Details →
v1.5.2-0.20230611173639-5c24baabf3ab 11 Jun 2023 none Apache-2.0 — Details →
v1.5.2-0.20230429133337-6284d14bb0b2 29 Apr 2023 none Apache-2.0 — Details →
v1.5.2-0.20230225180729-ffe9bcb4b91f 25 Feb 2023 none Apache-2.0 — Details →
v1.5.1 25 Feb 2023 none Apache-2.0 — Details →
v1.5.0 25 Feb 2023 none Apache-2.0 — Details →
v1.4.1-0.20230222212836-c7b837ea025f 22 Feb 2023 none Apache-2.0 — Details →
v1.3.1-0.20230129161615-1396000fa337 29 Jan 2023 none Apache-2.0 — Details →
v1.4.0 29 Jan 2023 none Apache-2.0 — Details →
v1.3.1-0.20230117042830-c193d6f52523 17 Jan 2023 none Apache-2.0 — Details →
v1.3.1-0.20230113204348-c39d8a2bb52b 13 Jan 2023 none Apache-2.0 — Details →
v1.3.1-0.20230113164644-fcba7ee4bc46 13 Jan 2023 none Apache-2.0 — Details →
v1.3.1-0.20230112121434-d52ddd1cec66 12 Jan 2023 none Apache-2.0 — Details →
v1.3.1-0.20221218140127-f9243d18e186 18 Dec 2022 none Apache-2.0 — Details →
v1.3.1-0.20221126155035-72d8dd551112 26 Nov 2022 none Apache-2.0 — Details →
v1.3.1-0.20221126153627-c9e35a01ef49 26 Nov 2022 none Apache-2.0 — Details →
v1.3.1-0.20220329024018-84bab94b78ce 29 Mar 2022 none Apache-2.0 — Details →
v1.3.1-0.20220220192642-4ddb62d38048 20 Feb 2022 none Apache-2.0 — Details →
v1.3.1-0.20220220164259-447f593ab14f 20 Feb 2022 none Apache-2.0 — Details →
v1.3.1-0.20220220164120-fc51f1982822 20 Feb 2022 none Apache-2.0 — Details →
v1.3.1-0.20220220163443-dd7cb0add0d4 20 Feb 2022 none Apache-2.0 — Details →
v1.3.1-0.20220219153941-d31d534090b2 19 Feb 2022 none Apache-2.0 — Details →
v1.3.1-0.20220219153905-7e48566384bd 19 Feb 2022 none Apache-2.0 — Details →
v1.3.1-0.20220219153703-41c98d657ada 19 Feb 2022 none Apache-2.0 — Details →
v1.2.1-0.20211220151224-9d876568708d 20 Dec 2021 none Apache-2.0 — Details →
v1.3.0 20 Dec 2021 none Apache-2.0 — Details →
v1.2.1-0.20210925142004-e0c18fe1a988 25 Sep 2021 none Apache-2.0 — Details →
v1.2.1-0.20210511164234-861de02e8871 11 May 2021 none Apache-2.0 — Details →
v1.2.0 10 May 2021 none Apache-2.0 — Details →
v1.1.1-0.20210210154840-ea9b1c5ce9d6 10 Feb 2021 none Apache-2.0 — Details →
v1.1.0 31 Jan 2021 none Apache-2.0 — Details →
v1.0.1-0.20210102153613-b137aeaef3bf 02 Jan 2021 none Apache-2.0 — Details →
v1.0.0 22 Sep 2019 none Apache-2.0 — Details →

All 42 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 github.com/ashanbrown/forbidigo

No vulnerability write-ups match this view

Search all 0 in the database →

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/ashanbrown/forbidigo

Is github.com/ashanbrown/forbidigo safe to use?

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

Vulert scores github.com/ashanbrown/forbidigo 55/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/ashanbrown/forbidigo affected?

No. v1.6.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/ashanbrown/forbidigo should I use?

v1.6.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/ashanbrown/forbidigo have?

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

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

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