Vulnerability Database · Go · Package report
github.com/gregdel/pushover: vulnerability history, versions and safety
github.com/gregdel/pushover 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/gregdel/pushover v1.4.0 i
Updated on 23 Oct 2026
Good news: v1.4.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Niche
- Community Inactive
What to do: Stay on v1.4.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.4.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.4.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 157 i
- OpenSSF scorecard 1/10 i
- Last release 13 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/gregdel/pushover, 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.
- v1.4.0 22 Sep 2025
- v1.3.1 29 Apr 2024
- v1.3.1-0.20240429110454-67e8cfdefddd 29 Apr 2024
- v1.2.2-0.20230907131946-216778598459 07 Sep 2023
- v1.3.0 07 Sep 2023
- v1.2.1 21 Aug 2023
- v1.2.1-0.20230821122533-99814631f6e2 21 Aug 2023
- v1.1.1-0.20211021122135-1025e0ddff2f 21 Oct 2021
- v1.2.0 21 Oct 2021
- v1.1.1-0.20210518213217-8681317e9650 18 May 2021
- v1.1.0 10 May 2021
- v0.0.0-20210420080121-f84e8ffafef5 20 Apr 2021
- v1.0.0 20 Apr 2021
- v0.0.0-20210216095829-2131362cb888 16 Feb 2021
- v0.0.0-20201104094836-ddbe0c1d3a38 04 Nov 2020
- v0.0.0-20201013155731-103e4d5fac63 13 Oct 2020
- v0.0.0-20200820121613-505cfd60a340 20 Aug 2020
- v0.0.0-20200416074932-c8ad547caed4 16 Apr 2020
- v0.0.0-20200330145937-ee607c681498 30 Mar 2020
- v0.0.0-20190217183207-15d3fef40636 17 Feb 2019
- v0.0.0-20180208231006-039e91d2e339 08 Feb 2018
- v0.0.0-20180208231006-1e03358b8e7e 08 Feb 2018
- v0.0.0-20161219170206-3c2e00dda05a 19 Dec 2016
- v0.0.0-20160618163533-f24f6bc84e4c 18 Jun 2016
- v0.0.0-20150828135018-047451b7c04d 28 Aug 2015
- v0.0.0-20150824101824-9232bff72857 24 Aug 2015
- v0.0.0-20150219154801-a1ec0217e05d 19 Feb 2015
All 27 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/gregdel/pushover
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/gregdel/pushover
Is github.com/gregdel/pushover safe to use?
Vulert has no vulnerabilities on record for github.com/gregdel/pushover 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/gregdel/pushover's Vulert package health score?
Vulert scores github.com/gregdel/pushover 59/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/gregdel/pushover affected?
No. v1.4.0, 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/gregdel/pushover should I use?
v1.4.0 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/gregdel/pushover have?
0 vulnerabilities are recorded for github.com/gregdel/pushover 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/gregdel/pushover vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/gregdel/pushover 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/gregdel/pushover 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/gregdel/pushover for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/gregdel/pushover version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.