Vulnerability Database · Go · Package report
github.com/zcalusic/sysinfo: vulnerability history, versions and safety
github.com/zcalusic/sysinfo 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/zcalusic/sysinfo v1.1.3 i
Updated on 23 Oct 2026
Good news: v1.1.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Widely used
- Community Quiet
What to do: Stay on v1.1.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 580 i
- OpenSSF scorecard 2/10 i
- Last release 23 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/zcalusic/sysinfo, 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.1.4-0.20241209081229-64129099fd65 09 Dec 2024
- v1.1.4-0.20241121204448-9aaf06850e5f 21 Nov 2024
- v1.1.3 21 Nov 2024
- v1.1.2 18 Sep 2024
- v1.1.2-0.20240917091656-db747cd0c82a 17 Sep 2024
- v1.1.1 17 Sep 2024
- v1.1.0 30 May 2024
- v1.0.4-0.20240530144540-fef37ed7deb6 30 May 2024
- v1.0.3 30 May 2024
- v1.0.2 20 Oct 2023
- v0.0.0-20230629082319-4ca1cf84ff7c 29 Jun 2023
- v1.0.1 29 Jun 2023
- v1.0.1-0.20230628133539-22c647fbef9d 28 Jun 2023
- v1.0.0 28 May 2023
- v0.9.6-0.20220805135214-99e836ba64f2 05 Aug 2022
- v0.9.6-0.20220321182531-30c5fd75386a 21 Mar 2022
- v0.9.6-0.20220302192107-812ca38aef42 02 Mar 2022
- v0.9.6-0.20220131223100-5209c432cfce 31 Jan 2022
- v0.0.0-20210905121133-6fa2f969a900 05 Sep 2021
- v0.9.5 05 Sep 2021
- v0.0.0-20210905093946-95c83945750a 05 Sep 2021
- v0.0.0-20210905085300-621f401b6f29 05 Sep 2021
- v0.0.0-20210831153053-2c6e1d254246 31 Aug 2021
- v0.9.4 31 Aug 2021
- v0.0.0-20210609180555-aff387a52b3a 09 Jun 2021
- v0.9.4-0.20210609180555-aff387a52b3a 09 Jun 2021
- v0.0.0-20210226105846-b810d137e525 26 Feb 2021
- v0.9.4-0.20210226105846-b810d137e525 26 Feb 2021
- v0.0.0-20201228191146-22fe1fd10b0f 28 Dec 2020
- v0.9.4-0.20201228191146-22fe1fd10b0f 28 Dec 2020
- v0.0.0-20200820110305-ef1bb2697bc2 20 Aug 2020
- v0.9.4-0.20200820110305-ef1bb2697bc2 20 Aug 2020
- v0.0.0-20200228145645-a159d7cc708b 28 Feb 2020
- v0.9.4-0.20200228145645-a159d7cc708b 28 Feb 2020
- v0.0.0-20200109185024-6491b6eabd49 09 Jan 2020
- v0.9.3 09 Jan 2020
- v0.0.0-20200109181100-45a03b2e1da8 09 Jan 2020
- v0.0.0-20200109175326-f87c764335c5 09 Jan 2020
- v0.0.0-20190913181835-ba6cb5edfaf3 13 Sep 2019
- v0.9.3-0.20190913181835-ba6cb5edfaf3 13 Sep 2019
- v0.0.0-20190429151633-fbadb57345c2 29 Apr 2019
- v0.9.3-0.20190429151633-fbadb57345c2 29 Apr 2019
- v0.0.0-20190218075354-591bbf422ee7 18 Feb 2019
- v0.0.0-20181028214501-f16b4d765f2e 28 Oct 2018
- v0.9.3-0.20181028214501-f16b4d765f2e 28 Oct 2018
- v0.0.0-20180930185032-52cd3f4affd5 30 Sep 2018
- v0.9.2 30 Sep 2018
- v0.0.0-20180218134502-7a16547e0bde 18 Feb 2018
- v0.9.2-0.20180218134502-7a16547e0bde 18 Feb 2018
- v0.0.0-20171010170106-cb55f814b6ba 10 Oct 2017
- v0.9.2-0.20171010170106-cb55f814b6ba 10 Oct 2017
- v0.9.2-0.20170825074115-c932490cd519 25 Aug 2017
- v0.9.1 24 Sep 2016
All 53 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/zcalusic/sysinfo
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/zcalusic/sysinfo
Is github.com/zcalusic/sysinfo safe to use?
Vulert has no vulnerabilities on record for github.com/zcalusic/sysinfo 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/zcalusic/sysinfo's Vulert package health score?
Vulert scores github.com/zcalusic/sysinfo 69/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/zcalusic/sysinfo affected?
No. v1.1.3, 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/zcalusic/sysinfo should I use?
v1.1.3 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/zcalusic/sysinfo have?
0 vulnerabilities are recorded for github.com/zcalusic/sysinfo 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/zcalusic/sysinfo vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/zcalusic/sysinfo 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/zcalusic/sysinfo 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/zcalusic/sysinfo for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/zcalusic/sysinfo version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.