Vulnerability Database · Go · Package report
github.com/facebookgo/atomicfile: vulnerability history, versions and safety
github.com/facebookgo/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/facebookgo/atomicfile v0.0.0-20151019160806-2de1f203e7d5 i
Updated on 23 Oct 2026
Good news: v0.0.0-20151019160806-2de1f203e7d5, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Unmaintained
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20151019160806-2de1f203e7d5 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20151019160806-2de1f203e7d5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20151019160806-2de1f203e7d5 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 51 i
- Last release 132 months ago i
- Licence BSD-3-Clause 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/facebookgo/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.0.0-20151019160806-2de1f203e7d5 19 Oct 2015
- v0.0.0-20150616183659-114d641d45b3 16 Jun 2015
- v0.0.0-20150612182741-82397bd18e99 12 Jun 2015
- v0.0.0-20140711061356-6f117f2e7f22 11 Jul 2014
- v0.0.0-20140524013628-2f9e55a6f340 24 May 2014
- v0.0.0-20140402214850-c5e31f42814b 02 Apr 2014
- v0.0.0-20131106013620-b4662ba4932c 06 Nov 2013
- v0.0.0-20130802230620-560064ed31c4 02 Aug 2013
- v0.0.0-20130222025725-00e2d4849261 22 Feb 2013
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.0-20151019160806-2de1f203e7d5 | 19 Oct 2015 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20150616183659-114d641d45b3 | 16 Jun 2015 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20150612182741-82397bd18e99 | 12 Jun 2015 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20140711061356-6f117f2e7f22 | 11 Jul 2014 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20140524013628-2f9e55a6f340 | 24 May 2014 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20140402214850-c5e31f42814b | 02 Apr 2014 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20131106013620-b4662ba4932c | 06 Nov 2013 | none | Apache-2.0 | — | Details → |
| v0.0.0-20130802230620-560064ed31c4 | 02 Aug 2013 | none | — | — | Details → |
| v0.0.0-20130222025725-00e2d4849261 | 22 Feb 2013 | none | — | — | Details → |
All 9 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/facebookgo/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/facebookgo/atomicfile
Is github.com/facebookgo/atomicfile safe to use?
Vulert has no vulnerabilities on record for github.com/facebookgo/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/facebookgo/atomicfile's Vulert package health score?
Vulert scores github.com/facebookgo/atomicfile 57/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/facebookgo/atomicfile affected?
No. v0.0.0-20151019160806-2de1f203e7d5, 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/facebookgo/atomicfile should I use?
v0.0.0-20151019160806-2de1f203e7d5 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/facebookgo/atomicfile have?
0 vulnerabilities are recorded for github.com/facebookgo/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/facebookgo/atomicfile vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/facebookgo/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/facebookgo/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/facebookgo/atomicfile for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/facebookgo/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.