VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/natefinch/atomic: vulnerability history, versions and safety

github.com/natefinch/atomic 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/natefinch/atomic vulnerabilities

Vulert verdict on github.com/natefinch/atomic v1.0.1 i

Updated on 23 Oct 2026

Good news: v1.0.1, the version you would install today, has no known vulnerabilities.

Package health score 47/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Inactive

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

  • Current release v1.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 211 i
  • OpenSSF scorecard 1/10 i
  • Last release 63 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/natefinch/atomic, 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-20210628180137-59b8c279e6d5 28 Jun 2021 none MIT — Details →
v1.0.1 28 Jun 2021 none MIT — Details →
v1.0.1-0.20210628180137-59b8c279e6d5 28 Jun 2021 none MIT — Details →
v1.0.0 27 Jun 2021 none MIT — Details →
v0.0.0-20210627155326-85a124586cef 27 Jun 2021 none MIT — Details →
v0.0.0-20200526193002-18c0533a5b09 26 May 2020 none MIT — Details →
v0.0.0-20200526030137-9436caf85d98 26 May 2020 none MIT — Details →
v0.0.0-20200202150604-6118b2a56c9b 02 Feb 2020 none MIT — Details →
v0.0.0-20190722202613-b22971ea520c 22 Jul 2019 none MIT — Details →
v0.0.0-20150920032501-a62ce929ffcc 20 Sep 2015 none MIT — Details →
v0.0.0-20150817170333-7ff6931586af 17 Aug 2015 none MIT — Details →
v0.0.0-20150803131534-7245c8604605 03 Aug 2015 none MIT — Details →
v0.0.0-20150803051437-3381814b64ac 03 Aug 2015 none MIT — Details →

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.

03 Vulnerabilities

Recorded vulnerabilities for github.com/natefinch/atomic

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/natefinch/atomic

Is github.com/natefinch/atomic safe to use?

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

Vulert scores github.com/natefinch/atomic 47/100, which reads as risky. 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/natefinch/atomic affected?

No. v1.0.1, 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/natefinch/atomic should I use?

v1.0.1 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/natefinch/atomic have?

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

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

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