Vulnerability Database · Go · Package report
github.com/skeema/knownhosts: vulnerability history, versions and safety
github.com/skeema/knownhosts 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/skeema/knownhosts v1.3.3 i
Updated on 23 Oct 2026
Good news: v1.3.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.3.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.3.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.3.3 — 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 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/skeema/knownhosts, 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.
- v1.3.3 27 Aug 2026
- v1.3.2 07 Oct 2025
- v1.3.2-0.20250613194253-5b6f59f4b742 13 Jun 2025
- v1.3.2-0.20250319193710-e3098efa96b0 19 Mar 2025
- v1.3.2-0.20250306195937-a8761da3f2cc 06 Mar 2025
- v1.3.1 29 Jan 2025
- v1.3.1-0.20250129223959-93146c84bcb6 29 Jan 2025
- v1.3.1-0.20240722211337-0f2fe42f5c26 22 Jul 2024
- v1.3.0 16 Jul 2024
- v1.2.3-0.20240712210303-7c797a490676 12 Jul 2024
- v1.2.3-0.20240703225606-5832aa8abbe1 03 Jul 2024
- v1.2.2 12 Mar 2024
- v1.2.2-0.20240311195626-f2b518cbd77b 11 Mar 2024
- v1.2.1 18 Sep 2023
- v1.2.1-0.20230918194709-3a35d9f4bebf 18 Sep 2023
- v1.2.1-0.20230916192230-09454b7d5683 16 Sep 2023
- v1.1.2-0.20230710201936-903aab75389f 10 Jul 2023
- v1.2.0 10 Jul 2023
- v1.1.2-0.20230707234735-619ef88d66f2 07 Jul 2023
- v1.1.1 12 May 2023
- v1.1.1-0.20230110232358-5dcbe52347da 10 Jan 2023
- v1.1.0 18 Jun 2022
- v1.0.0 17 Jun 2022
- v0.0.0-20220617231258-2f9421f72e42 17 Jun 2022
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v1.3.3 | 27 Aug 2026 | none | Apache-2.0 | — | Details → |
| v1.3.2 | 07 Oct 2025 | none | Apache-2.0 | — | Details → |
| v1.3.2-0.20250613194253-5b6f59f4b742 | 13 Jun 2025 | none | Apache-2.0 | — | Details → |
| v1.3.2-0.20250319193710-e3098efa96b0 | 19 Mar 2025 | none | Apache-2.0 | — | Details → |
| v1.3.2-0.20250306195937-a8761da3f2cc | 06 Mar 2025 | none | Apache-2.0 | — | Details → |
| v1.3.1 | 29 Jan 2025 | none | Apache-2.0 | — | Details → |
| v1.3.1-0.20250129223959-93146c84bcb6 | 29 Jan 2025 | none | Apache-2.0 | — | Details → |
| v1.3.1-0.20240722211337-0f2fe42f5c26 | 22 Jul 2024 | none | Apache-2.0 | — | Details → |
| v1.3.0 | 16 Jul 2024 | none | Apache-2.0 | — | Details → |
| v1.2.3-0.20240712210303-7c797a490676 | 12 Jul 2024 | none | Apache-2.0 | — | Details → |
| v1.2.3-0.20240703225606-5832aa8abbe1 | 03 Jul 2024 | none | Apache-2.0 | — | Details → |
| v1.2.2 | 12 Mar 2024 | none | Apache-2.0 | — | Details → |
| v1.2.2-0.20240311195626-f2b518cbd77b | 11 Mar 2024 | none | Apache-2.0 | — | Details → |
| v1.2.1 | 18 Sep 2023 | none | Apache-2.0 | — | Details → |
| v1.2.1-0.20230918194709-3a35d9f4bebf | 18 Sep 2023 | none | Apache-2.0 | — | Details → |
| v1.2.1-0.20230916192230-09454b7d5683 | 16 Sep 2023 | none | Apache-2.0 | — | Details → |
| v1.1.2-0.20230710201936-903aab75389f | 10 Jul 2023 | none | Apache-2.0 | — | Details → |
| v1.2.0 | 10 Jul 2023 | none | Apache-2.0 | — | Details → |
| v1.1.2-0.20230707234735-619ef88d66f2 | 07 Jul 2023 | none | Apache-2.0 | — | Details → |
| v1.1.1 | 12 May 2023 | none | Apache-2.0 | — | Details → |
| v1.1.1-0.20230110232358-5dcbe52347da | 10 Jan 2023 | none | Apache-2.0 | — | Details → |
| v1.1.0 | 18 Jun 2022 | none | Apache-2.0 | — | Details → |
| v1.0.0 | 17 Jun 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20220617231258-2f9421f72e42 | 17 Jun 2022 | none | Apache-2.0 | — | Details → |
All 24 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/skeema/knownhosts
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/skeema/knownhosts
Is github.com/skeema/knownhosts safe to use?
Vulert has no vulnerabilities on record for github.com/skeema/knownhosts 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/skeema/knownhosts's Vulert package health score?
Vulert scores github.com/skeema/knownhosts 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/skeema/knownhosts affected?
No. v1.3.3, 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/skeema/knownhosts should I use?
v1.3.3 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/skeema/knownhosts have?
0 vulnerabilities are recorded for github.com/skeema/knownhosts 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/skeema/knownhosts vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/skeema/knownhosts 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/skeema/knownhosts 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/skeema/knownhosts for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/skeema/knownhosts version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.