Vulnerability Database · Go · Package report

atomicgo.dev/keyboard: vulnerability history, versions and safety

atomicgo.dev/keyboard 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 atomicgo.dev/keyboard v0.2.10 i

Updated on 23 Oct 2026

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

Package health score 66/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Inactive

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

  • Current release v0.2.10 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 109 i
  • OpenSSF scorecard 2/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 atomicgo.dev/keyboard, 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.2.11-0.20261010040932-e2182d4dc6b5 10 Oct 2026 none MIT — Details →
v0.2.10 06 May 2026 none MIT — Details →
v0.2.10-0.20260426165941-4b92e076b6ae 26 Apr 2026 none MIT — Details →
v0.2.10-0.20240808170423-80582ee4a473 08 Aug 2024 none MIT — Details →
v0.2.10-0.20240713225620-1ae7c57ffa34 13 Jul 2024 none MIT — Details →
v0.2.10-0.20240626110925-689a24ddfbc7 26 Jun 2024 none MIT — Details →
v0.2.10-0.20231105030551-c861ae9c8e7e 05 Nov 2023 none MIT — Details →
v0.2.10-0.20230607163628-9c099e7020fc 07 Jun 2023 none MIT — Details →
v0.2.9 10 Jan 2023 none MIT — Details →
v0.2.9-0.20221009021606-5a0753a6bfe0 09 Oct 2022 none MIT — Details →
v0.2.8 08 Jun 2022 none MIT — Details →
v0.2.6 05 Jun 2022 none MIT — Details →
v0.2.7 05 Jun 2022 none MIT — Details →
v0.2.5 05 Jun 2022 none MIT — Details →
v0.2.4 05 Jun 2022 none MIT — Details →
v0.2.3 05 Jun 2022 none MIT — Details →
v0.2.2 05 Jun 2022 none MIT — Details →
v0.2.1 05 Jun 2022 none MIT — Details →
v0.2.0 02 Jun 2022 none MIT — Details →
v0.1.0 02 Jun 2022 none MIT — Details →
v0.0.0-20220602003259-db1f258e5e4e 02 Jun 2022 none MIT — Details →
v0.0.0-20220602000030-5116972a6507 02 Jun 2022 none MIT — Details →

All 22 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 atomicgo.dev/keyboard

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 atomicgo.dev/keyboard

Is atomicgo.dev/keyboard safe to use?

Vulert has no vulnerabilities on record for atomicgo.dev/keyboard 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 atomicgo.dev/keyboard's Vulert package health score?

Vulert scores atomicgo.dev/keyboard 66/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 atomicgo.dev/keyboard affected?

No. v0.2.10, 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 atomicgo.dev/keyboard should I use?

v0.2.10 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 atomicgo.dev/keyboard have?

0 vulnerabilities are recorded for atomicgo.dev/keyboard 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 atomicgo.dev/keyboard vulnerabilities disclosed?

0 vulnerabilities were recorded for atomicgo.dev/keyboard 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 atomicgo.dev/keyboard 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 atomicgo.dev/keyboard for upcoming vulnerabilities?

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