Vulnerability Database · Go · Package report
github.com/groob/plist: vulnerability history, versions and safety
github.com/groob/plist 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/groob/plist v0.1.1 i
Updated on 23 Oct 2026
Good news: v0.1.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Niche
- Community Inactive
What to do: Stay on v0.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 63 i
- OpenSSF scorecard 3/10 i
- Last release 23 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/groob/plist, 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-20241127223127-099374376000 27 Nov 2024
- v0.1.2-0.20241127223127-099374376000 27 Nov 2024
- v0.1.1 12 Nov 2024
- v0.1.1-0.20241112211118-fd3c376b412d 12 Nov 2024
- v0.0.0-20220217120414-63fa881b19a5 17 Feb 2022
- v0.1.0 17 Feb 2022
- v0.0.0-20210519001750-9f754062e6d6 19 May 2021
- v0.0.0-20200425180238-0f631f258c01 25 Apr 2020
- v0.0.0-20200425172828-526b8c34977d 25 Apr 2020
- v0.0.0-20200425161518-7a4ce50472e5 25 Apr 2020
- v0.0.0-20200425044108-a0b62d10a813 25 Apr 2020
- v0.0.0-20200424174937-7e0188ed1a98 24 Apr 2020
- v0.0.0-20200424143601-71dd5bf1228d 24 Apr 2020
- v0.0.0-20200424143351-2de59f4820ef 24 Apr 2020
- v0.0.0-20190114192801-a99fbe489d03 14 Jan 2019
- v0.0.0-20180203051248-dd56909aee38 03 Feb 2018
- v0.0.0-20171204151034-2805b357fb23 04 Dec 2017
- v0.0.0-20171129141540-63337f8a3d79 29 Nov 2017
- v0.0.0-20171124190811-ca31a9049208 24 Nov 2017
- v0.0.0-20171013152701-7b367e0aa692 13 Oct 2017
- v0.0.0-20171011215546-567f2f5642de 11 Oct 2017
- v0.0.0-20170529165030-cd4f0bb61665 29 May 2017
- v0.0.0-20170301040010-43f06cf03cbc 01 Mar 2017
- v0.0.0-20161130042027-a4f34fbabd91 30 Nov 2016
- v0.0.0-20160524011611-e9ca5cd12940 24 May 2016
- v0.0.0-20160304051658-960422c558dc 04 Mar 2016
- v0.0.0-20160303224527-556de4b17982 03 Mar 2016
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/groob/plist
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/groob/plist
Is github.com/groob/plist safe to use?
Vulert has no vulnerabilities on record for github.com/groob/plist 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/groob/plist's Vulert package health score?
Vulert scores github.com/groob/plist 63/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/groob/plist affected?
No. v0.1.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/groob/plist should I use?
v0.1.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/groob/plist have?
0 vulnerabilities are recorded for github.com/groob/plist 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/groob/plist vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/groob/plist 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/groob/plist 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/groob/plist for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/groob/plist version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.