Vulnerability Database · Go · Package report
github.com/icza/dyno: vulnerability history, versions and safety
github.com/icza/dyno is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/icza/dyno v0.0.0-20260912175837-51f8ab52fd15 i
Updated on 23 Oct 2026
Good news: v0.0.0-20260912175837-51f8ab52fd15, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20260912175837-51f8ab52fd15 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20260912175837-51f8ab52fd15 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20260912175837-51f8ab52fd15 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 143 i
- OpenSSF scorecard 2/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 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/icza/dyno, 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.
- v0.0.0-20260912175837-51f8ab52fd15 12 Sep 2026
- v0.0.0-20230330125955-09f820a8d9c0 30 Mar 2023
- v0.0.0-20230330125918-0761be1882a9 30 Mar 2023
- v0.0.0-20220812133438-f0b6f8a18845 12 Aug 2022
- v0.0.0-20210726202311-f1bafe5d9996 26 Jul 2021
- v0.0.0-20200205103839-49cb13720835 05 Feb 2020
- v0.0.0-20180601094105-0c96289f9585 01 Jun 2018
- v0.0.0-20180601090654-0a3d726dd80d 01 Jun 2018
- v0.0.0-20180531123050-09b6e9d16570 31 May 2018
- v0.0.0-20180119125910-15f794d2c82a 19 Jan 2018
- v0.0.0-20180119122641-0e6e615ffb04 19 Jan 2018
- v0.0.0-20180103154816-50ce771dbb36 03 Jan 2018
- v0.0.0-20171218154035-1a06e153be70 18 Dec 2017
All 13 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/icza/dyno
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
Questions
About github.com/icza/dyno
Is github.com/icza/dyno safe to use?
Vulert has no vulnerabilities on record for github.com/icza/dyno 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/icza/dyno's Vulert package health score?
Vulert scores github.com/icza/dyno 70/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/icza/dyno affected?
No. v0.0.0-20260912175837-51f8ab52fd15, 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/icza/dyno should I use?
v0.0.0-20260912175837-51f8ab52fd15 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/icza/dyno have?
0 vulnerabilities are recorded for github.com/icza/dyno 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/icza/dyno vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/icza/dyno 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/icza/dyno 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/icza/dyno for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/icza/dyno version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.