VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/t3rm1n4l/go-mega: vulnerability history, versions and safety

github.com/t3rm1n4l/go-mega 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.

See all github.com/t3rm1n4l/go-mega vulnerabilities

Vulert verdict on github.com/t3rm1n4l/go-mega v0.0.0-20260717075258-c6acd6a5bd04 i

Updated on 23 Oct 2026

Good news: v0.0.0-20260717075258-c6acd6a5bd04, the version you would install today, has no known vulnerabilities.

Package health score 72/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release v0.0.0-20260717075258-c6acd6a5bd04 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 216 i
  • OpenSSF scorecard 2/10 i
  • Last release 3 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 github.com/t3rm1n4l/go-mega, 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
v0.0.0-20260717075258-c6acd6a5bd04 17 Jul 2026 none MIT — Details →
v0.0.0-20260630094356-4de2f127f34a 30 Jun 2026 none MIT — Details →
v0.0.0-20251120131202-6845944c051c 20 Nov 2025 none MIT — Details →
v0.0.0-20251118171052-6e4a0d75c6fe 18 Nov 2025 none MIT — Details →
v0.0.0-20251031123324-a804aaa87491 31 Oct 2025 none MIT — Details →
v0.0.0-20250926104142-34ee130c9620 26 Sep 2025 none MIT — Details →
v0.0.0-20250926104142-55f58483cf02 26 Sep 2025 none MIT — Details →
v0.0.0-20250926104142-8a29a3a6b34d 26 Sep 2025 none MIT — Details →
v0.0.0-20250926104142-ccb8d3498e6c 26 Sep 2025 none MIT — Details →
v0.0.0-20241213151442-a19cff0ec7b5 13 Dec 2024 none MIT — Details →
v0.0.0-20241213150454-ec0027fb0002 13 Dec 2024 none MIT — Details →
v0.0.0-20240219080617-d494b6a8ace7 19 Feb 2024 none MIT — Details →
v0.0.0-20230228171823-a01a2cda13ca 28 Feb 2023 none MIT — Details →
v0.0.0-20230228110818-5af6e0a8fa3e 28 Feb 2023 none MIT — Details →
v0.0.0-20230220145126-b87ebf5801d8 20 Feb 2023 none MIT — Details →
v0.0.0-20220725095014-c4e0c2b5debf 25 Jul 2022 none MIT — Details →
v0.0.0-20200416171014-ffad7fcb44b8 16 Apr 2020 none MIT — Details →
v0.0.0-20200301084900-c07c6adb9309 01 Mar 2020 none MIT — Details →
v0.0.0-20200117211730-79a813bb328d 17 Jan 2020 none MIT — Details →
v0.0.0-20200111163430-ad0abe77ec81 11 Jan 2020 none MIT — Details →
v0.0.0-20191014094753-e8695d78299a 14 Oct 2019 none MIT — Details →
v0.0.0-20190528125457-55e675378686 28 May 2019 none MIT — Details →
v0.0.0-20190430100803-72151b53bb44 30 Apr 2019 none — — Details →
v0.0.0-20190430094501-ba3fe8690a46 30 Apr 2019 none — — Details →
v0.0.0-20190205172012-55a226cf41da 05 Feb 2019 none — — Details →
v0.0.0-20190204171941-1b8ac3503be8 04 Feb 2019 none — — Details →
v0.0.0-20190204165317-98274d298882 04 Feb 2019 none — — Details →
v0.0.0-20180817194457-854bf31d998b 17 Aug 2018 none — — Details →
v0.0.0-20180630095652-57978a63bd3f 30 Jun 2018 none — — Details →
v0.0.0-20180426134857-3ba49835f4db 26 Apr 2018 none — — Details →
v0.0.0-20180411190657-4e68b16e97ff 11 Apr 2018 none — — Details →
v0.0.0-20130918055232-195f18ccf362 18 Sep 2013 none — — Details →
v0.0.0-20130614104017-787affd5997c 14 Jun 2013 none — — 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.

03 Vulnerabilities

Recorded vulnerabilities for github.com/t3rm1n4l/go-mega

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/t3rm1n4l/go-mega

Is github.com/t3rm1n4l/go-mega safe to use?

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

Vulert scores github.com/t3rm1n4l/go-mega 72/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 github.com/t3rm1n4l/go-mega affected?

No. v0.0.0-20260717075258-c6acd6a5bd04, 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/t3rm1n4l/go-mega should I use?

v0.0.0-20260717075258-c6acd6a5bd04 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/t3rm1n4l/go-mega have?

0 vulnerabilities are recorded for github.com/t3rm1n4l/go-mega 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/t3rm1n4l/go-mega vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/t3rm1n4l/go-mega 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/t3rm1n4l/go-mega 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/t3rm1n4l/go-mega for upcoming vulnerabilities?

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