Vulnerability Database · Go · Package report
github.com/timakin/bodyclose: vulnerability history, versions and safety
github.com/timakin/bodyclose 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/timakin/bodyclose v0.0.0-20260923065923-98ded9ab4ef2 i
Updated on 23 Oct 2026
Good news: v0.0.0-20260923065923-98ded9ab4ef2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on v0.0.0-20260923065923-98ded9ab4ef2 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20260923065923-98ded9ab4ef2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20260923065923-98ded9ab4ef2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 323 i
- OpenSSF scorecard 2/10 i
- Last release 1 month 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/timakin/bodyclose, 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-20260923065923-98ded9ab4ef2 23 Sep 2026
- v0.0.0-20260904121052-b428559a42c3 04 Sep 2026
- v0.0.0-20260904120145-14f5f2e7069e 04 Sep 2026
- v0.0.0-20260904120128-ca37ec723ca7 04 Sep 2026
- v0.0.0-20260723120731-857993a2939c 23 Jul 2026
- v0.0.0-20260723101024-76f1f8bf15e0 23 Jul 2026
- v0.0.0-20260129054331-73d1f95b84b4 29 Jan 2026
- v0.0.0-20250609054347-742a4adeb981 09 Jun 2025
- v0.0.0-20250609044040-fe404153c256 09 Jun 2025
- v0.0.0-20250609044025-093ba82372c8 09 Jun 2025
- v0.0.0-20250517082039-5006729c42b1 17 May 2025
- v0.0.0-20250517070453-106f9f607d29 17 May 2025
- v0.0.0-20241222091800-1db5c5ca4d67 22 Dec 2024
- v0.0.0-20241126224809-21c25cacdf21 26 Nov 2024
- v0.0.0-20241017074824-adbc21e6bf36 17 Oct 2024
- v0.0.0-20241017074812-ed6a65f985e3 17 Oct 2024
- v0.0.0-20241017074800-699fab16ddd4 17 Oct 2024
- v0.0.0-20241017074748-0b90aa17e250 17 Oct 2024
- v0.0.0-20241017074735-a60ea0241848 17 Oct 2024
- v0.0.0-20240909054209-461c422de67f 09 Sep 2024
- v0.0.0-20240909053022-215355d72c2d 09 Sep 2024
- v0.0.0-20240907071853-d162f46f2f5a 07 Sep 2024
- v0.0.0-20240905081703-754c31111374 05 Sep 2024
- v0.0.0-20240904051357-bb14ecdbdf95 04 Sep 2024
- v0.0.0-20240125160201-f835fa56326a 25 Jan 2024
- v0.0.0-20240125160034-c0b502645112 25 Jan 2024
- v0.0.0-20231120203328-707eb7641b83 20 Nov 2023
- v0.0.0-20231019133200-76e9e9197533 19 Oct 2023
- v0.0.0-20230421092635-574207250966 21 Apr 2023
- v0.0.0-20230419012055-cdd6cc35a43a 19 Apr 2023
- v0.0.0-20230419011455-f7423e81ddcc 19 Apr 2023
- v0.0.0-20230210223729-d0a283b69002 10 Feb 2023
- v0.0.0-20221125081123-e39cf3fc478e 25 Nov 2022
- v0.0.0-20221125081113-c933b9a77989 25 Nov 2022
- v0.0.0-20221106201742-7e6d4ea2ee7a 06 Nov 2022
- v0.0.0-20220615215514-ed34b7df51b8 15 Jun 2022
- v0.0.0-20220615215333-b641ab67f069 15 Jun 2022
- v0.0.0-20220316194516-8431e0258bab 16 Mar 2022
- v0.0.0-20210704033933-f49887972144 04 Jul 2021
- v0.0.0-20210703130759-4a3e3990d3bf 03 Jul 2021
- v0.0.0-20200424151742-cb6215831a94 24 Apr 2020
- v0.0.0-20200324105812-b2984ad28889 24 Mar 2020
- v0.0.0-20190930140734-f7f2e9bca95e 30 Sep 2019
- v0.0.0-20190927095750-dde62d2d6b99 27 Sep 2019
- v0.0.0-20190926151346-866fdb772e33 26 Sep 2019
- v0.0.0-20190924091105-43b3ff1b0de0 24 Sep 2019
- v0.0.0-20190910154619-42cacc375707 10 Sep 2019
- v0.0.0-20190721030226-87058b9bfcec 21 Jul 2019
- v0.0.0-20190714144026-65da19158fa2 14 Jul 2019
- v0.0.0-20190713050349-d96ec0dee822 13 Jul 2019
- v0.0.0-20190609232652-41875bbb2ce1 09 Jun 2019
- v0.0.0-20190609231156-2bfd3fed5e52 09 Jun 2019
- v0.0.0-20190407043127-4a873e97b2bb 07 Apr 2019
- v0.0.0-20190406033815-db267c5b5aec 06 Apr 2019
- v0.0.0-20190404232845-a8d3ef104b1d 04 Apr 2019
- v0.0.0-20190330154753-8ad59793c6e0 30 Mar 2019
- v0.0.0-20190329150117-6644437f9794 29 Mar 2019
- v0.0.0-20190328152847-3f7157a70969 28 Mar 2019
- v0.0.0-20190327034954-2847da23150a 27 Mar 2019
- v0.0.0-20190326093615-926c9cae6aeb 26 Mar 2019
- v0.0.0-20190325235924-8f27cf61a308 25 Mar 2019
- v0.0.0-20190324133118-c872eb8f223d 24 Mar 2019
- v0.0.0-20190323120648-e60688d5bdf3 23 Mar 2019
- v0.0.0-20190323111206-572134a6bac8 23 Mar 2019
All 64 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/timakin/bodyclose
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/timakin/bodyclose
Is github.com/timakin/bodyclose safe to use?
Vulert has no vulnerabilities on record for github.com/timakin/bodyclose 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/timakin/bodyclose's Vulert package health score?
Vulert scores github.com/timakin/bodyclose 72/100, which reads as in good shape. 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/timakin/bodyclose affected?
No. v0.0.0-20260923065923-98ded9ab4ef2, 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/timakin/bodyclose should I use?
v0.0.0-20260923065923-98ded9ab4ef2 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/timakin/bodyclose have?
0 vulnerabilities are recorded for github.com/timakin/bodyclose 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/timakin/bodyclose vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/timakin/bodyclose 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/timakin/bodyclose 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/timakin/bodyclose for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/timakin/bodyclose version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.