Vulnerability Database · Go · Package report

github.com/vulsio/go-cti: vulnerability history, versions and safety

github.com/vulsio/go-cti 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/vulsio/go-cti v0.3.6 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v0.3.6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 35 i
  • OpenSSF scorecard 4/10 i
  • Last release 5 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/vulsio/go-cti, 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.3.6 11 May 2026 none MIT — Details →
v0.3.5 11 May 2026 none MIT — Details →
v0.3.4 03 Feb 2026 none MIT — Details →
v0.3.3 08 Dec 2025 none MIT — Details →
v0.3.2 24 Sep 2025 none MIT — Details →
v0.3.1 01 Jul 2025 none MIT — Details →
v0.3.0 24 Jun 2025 none MIT — Details →
v0.2.1-0.20250317020119-aaf4cf09492e 17 Mar 2025 none MIT — Details →
v0.2.0 18 Feb 2025 none MIT — Details →
v0.0.5-0.20240927064618-56efee318538 27 Sep 2024 none MIT — Details →
v0.1.0 27 Sep 2024 none MIT — Details →
v0.0.5-0.20240708124012-4198383fc0ff 08 Jul 2024 none MIT — Details →
v0.0.5-0.20240708053351-db7e01afff3e 08 Jul 2024 none MIT — Details →
v0.0.5-0.20240424060750-f4a904c9a50d 24 Apr 2024 none MIT — Details →
v0.0.0-20240318121747-822b3ef289cb 18 Mar 2024 none MIT — Details →
v0.0.5-0.20240318121747-822b3ef289cb 18 Mar 2024 none MIT — Details →
v0.0.5-0.20240208112427-2dc18a9115db 08 Feb 2024 none MIT — Details →
v0.0.5-0.20240108165911-1f1a194eece4 08 Jan 2024 none MIT — Details →
v0.0.5-0.20231217191918-27dd65e7bf4a 17 Dec 2023 none MIT — Details →
v0.0.5-0.20231017103759-59e022ddcd0e 17 Oct 2023 none MIT — Details →
v0.0.4 24 Jul 2023 none MIT — Details →
v0.0.4-0.20230724224303-1bfab8a369a4 24 Jul 2023 none MIT — Details →
v0.0.4-0.20230719130015-0a411d419c5d 19 Jul 2023 none MIT — Details →
v0.0.3 10 May 2023 none MIT — Details →
v0.0.3-0.20230427041012-30a536e7ee53 27 Apr 2023 none MIT — Details →
v0.0.3-0.20230426165117-48672409288c 26 Apr 2023 none MIT — Details →
v0.0.2 19 Feb 2023 none MIT — Details →
v0.0.2-0.20221030155613-e31ef31d11da 30 Oct 2022 none MIT — Details →
v0.0.0-20220613013115-8c7e57a6aa86 13 Jun 2022 none MIT — Details →
v0.0.2-0.20220613013115-8c7e57a6aa86 13 Jun 2022 none MIT — Details →
v0.0.2-0.20220518044749-16b62af96e42 18 May 2022 none MIT — Details →
v0.0.2-0.20220516025257-e25a75a02536 16 May 2022 none MIT — Details →
v0.0.0-20220420031859-386df10cf386 20 Apr 2022 none MIT — Details →
v0.0.1 20 Apr 2022 none MIT — Details →
v0.0.0-20220419232248-03cc0ecf383c 19 Apr 2022 none MIT — Details →
v0.0.0-20220414153043-0e9061e7c88d 14 Apr 2022 none MIT — Details →
v0.0.0-20220324003449-eb4ff918964b 24 Mar 2022 none MIT — Details →
v0.0.0-20210804143808-c933b817b863 04 Aug 2021 none MIT — Details →

All 38 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/vulsio/go-cti

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/vulsio/go-cti

Is github.com/vulsio/go-cti safe to use?

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

Vulert scores github.com/vulsio/go-cti 65/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/vulsio/go-cti affected?

No. v0.3.6, 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/vulsio/go-cti should I use?

v0.3.6 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/vulsio/go-cti have?

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

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

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