VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/bronze1man/goStrongswanVici: vulnerability history, versions and safety

github.com/bronze1man/goStrongswanVici 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/bronze1man/goStrongswanVici vulnerabilities

Vulert verdict on github.com/bronze1man/goStrongswanVici v0.0.0-20231128135937-211cef3b0b20 i

Updated on 23 Oct 2026

Good news: v0.0.0-20231128135937-211cef3b0b20, the version you would install today, has no known vulnerabilities.

Package health score 52/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v0.0.0-20231128135937-211cef3b0b20 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 39 i
  • OpenSSF scorecard 2/10 i
  • Last release 34 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/bronze1man/goStrongswanVici, 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-20231128135937-211cef3b0b20 28 Nov 2023 none MIT — Details →
v0.0.0-20221114103242-3f6dc524986c 14 Nov 2022 none MIT — Details →
v0.0.0-20221107021624-3aa475eebc4f 07 Nov 2022 none MIT — Details →
v0.0.0-20220622094615-37a38ce6eaeb 22 Jun 2022 none MIT — Details →
v0.0.0-20220330012221-41b373c8298a 30 Mar 2022 none MIT — Details →
v0.0.0-20210615051318-35664904df04 15 Jun 2021 none MIT — Details →
v0.0.0-20210612135823-e13b837c4c95 12 Jun 2021 none MIT — Details →
v0.0.0-20201105010758-936f38b697fd 05 Nov 2020 none MIT — Details →
v0.0.0-20201104070729-f9a9adbea19d 04 Nov 2020 none MIT — Details →
v0.0.0-20200818020849-44c89d86400e 18 Aug 2020 none MIT — Details →
v0.0.0-20200726124208-97949d8f2c8a 26 Jul 2020 none MIT — Details →
v0.0.0-20200726085931-feb91b1055b5 26 Jul 2020 none MIT — Details →
v0.0.0-20200615065859-ff78c6a7cf1f 15 Jun 2020 none MIT — Details →
v0.0.0-20200612214255-d29e3b46339e 12 Jun 2020 none MIT — Details →
v0.0.0-20191011010153-01da0e04f8c3 11 Oct 2019 none MIT — Details →
v0.0.0-20191008025824-989dda99ab2f 08 Oct 2019 none MIT — Details →
v0.0.0-20191001183117-7fd65e7a11d9 01 Oct 2019 none MIT — Details →
v0.0.0-20190921045355-4c81bd8d0bd5 21 Sep 2019 none MIT — Details →
v0.0.0-20190920145242-c85b083a78f8 20 Sep 2019 none MIT — Details →
v0.0.0-20190828090544-27d02f80ba40 28 Aug 2019 none MIT — Details →
v0.0.0-20190827172727-50129f84b242 27 Aug 2019 none MIT — Details →
v0.0.0-20190719015008-509f4b55344d 19 Jul 2019 none MIT — Details →
v0.0.0-20190718234201-bf0d16e0b675 18 Jul 2019 none MIT — Details →
v0.0.0-20180501004240-bf0f8669d78f 01 May 2018 none MIT — Details →
v0.0.0-20180429151852-4d73c5282477 29 Apr 2018 none MIT — Details →
v0.0.0-20171023001034-38352942833e 23 Oct 2017 none MIT — Details →
v0.0.0-20171013065002-4d72634a2f11 13 Oct 2017 none MIT — Details →
v0.0.0-20171012025651-50cf258398fa 12 Oct 2017 none MIT — Details →
v0.0.0-20170818013600-d445678a52b2 18 Aug 2017 none MIT — Details →
v0.0.0-20170804204113-6e28b242e1a7 04 Aug 2017 none MIT — Details →
v0.0.0-20170720215907-1febb634cdb6 20 Jul 2017 none MIT — Details →
v0.0.0-20170617200208-d9ba78075e24 17 Jun 2017 none MIT — Details →
v0.0.0-20170512150626-86f19d6abf56 12 May 2017 none MIT — Details →
v0.0.0-20170308154659-b703602ea4ec 08 Mar 2017 none MIT — Details →
v0.0.0-20151204142041-76db50e37f60 04 Dec 2015 none MIT — Details →
v0.0.0-20150806190704-351c39c09a28 06 Aug 2015 none MIT — Details →
v0.0.0-20150203110429-b3d9c5a94ce0 03 Feb 2015 none MIT — Details →
v0.0.0-20150121044947-e011c6ac8610 21 Jan 2015 none — — 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/bronze1man/goStrongswanVici

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/bronze1man/goStrongswanVici

Is github.com/bronze1man/goStrongswanVici safe to use?

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

Vulert scores github.com/bronze1man/goStrongswanVici 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 github.com/bronze1man/goStrongswanVici affected?

No. v0.0.0-20231128135937-211cef3b0b20, 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/bronze1man/goStrongswanVici should I use?

v0.0.0-20231128135937-211cef3b0b20 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/bronze1man/goStrongswanVici have?

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

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

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