Vulnerability Database · Go · Package report
github.com/creachadair/atomicfile: vulnerability history, versions and safety
github.com/creachadair/atomicfile 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/creachadair/atomicfile v0.4.2 i
Updated on 23 Oct 2026
Good news: v0.4.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Little adoption
- Community Quiet
What to do: Stay on v0.4.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.4.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.4.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 3 i
- OpenSSF scorecard 4/10 i
- Last release 3 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/creachadair/atomicfile, 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.4.3-0.20260901054524-186fd174158d 01 Sep 2026
- v0.4.2 10 Jul 2026
- v0.4.2-0.20260702150350-7250cf28a97a 02 Jul 2026
- v0.4.1 13 Feb 2026
- v0.4.1-0.20251106043647-5efc4f8d8de3 06 Nov 2025
- v0.4.0 23 Oct 2025
- v0.3.9-0.20251002031850-b5d329c261d1 02 Oct 2025
- v0.3.9-0.20250919154224-1dffff8e2be0 19 Sep 2025
- v0.3.9-0.20250908221700-0fa3a31cdc4d 08 Sep 2025
- v0.3.8 13 Mar 2025
- v0.3.7 23 Dec 2024
- v0.3.7-0.20241122165428-2bffcf5c6d48 22 Nov 2024
- v0.3.6 16 Nov 2024
- v0.3.6-0.20241116172132-af74d966bbf1 16 Nov 2024
- v0.3.6-0.20241109182923-63947374c7d5 09 Nov 2024
- v0.3.6-0.20240914153210-4a1e145b3af0 14 Sep 2024
- v0.3.6-0.20240828153610-52d6d86b379b 28 Aug 2024
- v0.3.5 11 Aug 2024
- v0.3.5-0.20240710143327-4b69ae8371d1 10 Jul 2024
- v0.3.5-0.20240623161212-aef99b6cfd69 23 Jun 2024
- v0.3.5-0.20240513171129-501382e007cc 13 May 2024
- v0.3.5-0.20240324161818-a9d8b752bc04 24 Mar 2024
- v0.3.4 23 Mar 2024
- v0.3.3 14 Jan 2024
- v0.3.3-0.20240114002415-98d1e12a2fa1 14 Jan 2024
- v0.3.2 25 Aug 2023
- v0.3.2-0.20230825010944-75dfb6ecc475 25 Aug 2023
- v0.3.1 11 Apr 2023
- v0.3.0 10 Apr 2023
- v0.2.9-0.20230205180751-f8528bc7b442 05 Feb 2023
- v0.2.8 27 Jan 2023
- v0.2.7 28 Jul 2022
- v0.2.7-0.20220505202113-42c8711cc581 05 May 2022
- v0.2.6 03 May 2022
- v0.2.6-0.20220426235456-e4427e5c1019 26 Apr 2022
- v0.2.6-0.20220416213235-2f161a5776ff 16 Apr 2022
- v0.2.6-0.20220416202332-29e8b7563c9c 16 Apr 2022
- v0.2.5 16 Apr 2022
- v0.2.4 12 Feb 2022
- v0.2.3 12 Feb 2022
- v0.2.3-0.20211028211521-febfe5169645 28 Oct 2021
- v0.2.3-0.20211028180445-3c26ec3a3ea9 28 Oct 2021
- v0.2.3-0.20211028172557-c14b087097bc 28 Oct 2021
- v0.2.3-0.20211024035345-16e9aac4d1e2 24 Oct 2021
- v0.2.2 14 Sep 2021
- v0.2.2-0.20210217180153-197d3822eaa2 17 Feb 2021
- v0.2.2-0.20201022201058-5f161b9cb2cb 22 Oct 2020
- v0.2.1 13 Aug 2020
- v0.2.0 10 Jun 2019
All 49 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/creachadair/atomicfile
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/creachadair/atomicfile
Is github.com/creachadair/atomicfile safe to use?
Vulert has no vulnerabilities on record for github.com/creachadair/atomicfile 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/creachadair/atomicfile's Vulert package health score?
Vulert scores github.com/creachadair/atomicfile 68/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/creachadair/atomicfile affected?
No. v0.4.2, 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/creachadair/atomicfile should I use?
v0.4.2 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/creachadair/atomicfile have?
0 vulnerabilities are recorded for github.com/creachadair/atomicfile 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/creachadair/atomicfile vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/creachadair/atomicfile 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/creachadair/atomicfile 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/creachadair/atomicfile for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/creachadair/atomicfile version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.