Vulnerability Database · Go · Package report
github.com/infobloxopen/go-trees: vulnerability history, versions and safety
github.com/infobloxopen/go-trees 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/infobloxopen/go-trees v0.0.0-20221216143356-66ceba885ebc i
Updated on 23 Oct 2026
Good news: v0.0.0-20221216143356-66ceba885ebc, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.0-20221216143356-66ceba885ebc or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20221216143356-66ceba885ebc too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20221216143356-66ceba885ebc — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 22 i
- OpenSSF scorecard 2/10 i
- Last release 46 months ago i
- Licence Apache-2.0 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/infobloxopen/go-trees, 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-20221216143356-66ceba885ebc 16 Dec 2022
- v0.0.0-20200715205103-96a057b8dfb9 15 Jul 2020
- v0.0.0-20200715042335-1e3afe01f6f2 15 Jul 2020
- v0.0.0-20190313150506-2af4e13f9062 13 Mar 2019
- v0.0.0-20181221165708-4a787b9d649c 21 Dec 2018
- v0.0.0-20180914094745-37f8b7da7ff6 14 Sep 2018
- v0.0.0-20180608122459-a1e500cde93c 08 Jun 2018
- v0.0.0-20180517093421-fb9cddb08aeb 17 May 2018
- v0.0.0-20180514143352-a560861770f1 14 May 2018
- v0.0.0-20180510095738-41e4ed70d8a4 10 May 2018
- v0.0.0-20180508175958-7d96a632eb72 08 May 2018
- v0.0.0-20180504142116-0bd5ebe38ca0 04 May 2018
- v0.0.0-20180428160237-1cfa68d22f3c 28 Apr 2018
- v0.0.0-20180423154034-5e11a56432a0 23 Apr 2018
- v0.0.0-20180228113306-ba3cf0abf6c4 28 Feb 2018
- v0.0.0-20180207141949-4d2dde9ff340 07 Feb 2018
- v0.0.0-20170728124626-7665ffa2af9c 28 Jul 2017
- v0.0.0-20170727195959-7e5ffc00a23e 27 Jul 2017
- v0.0.0-20170726151006-8ca407ad68db 26 Jul 2017
- v0.0.0-20170715121558-4978456d55af 15 Jul 2017
- v0.0.0-20170714152705-f749f7e34670 14 Jul 2017
- v0.0.0-20170629160456-9d4a1ff60b53 29 Jun 2017
- v0.0.0-20170619153858-400e45552f76 19 Jun 2017
- v0.0.0-20170616195708-c9a5c2e0175f 16 Jun 2017
- v0.0.0-20170615154900-d17a74ccc259 15 Jun 2017
All 25 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/infobloxopen/go-trees
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/infobloxopen/go-trees
Is github.com/infobloxopen/go-trees safe to use?
Vulert has no vulnerabilities on record for github.com/infobloxopen/go-trees 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/infobloxopen/go-trees's Vulert package health score?
Vulert scores github.com/infobloxopen/go-trees 50/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/infobloxopen/go-trees affected?
No. v0.0.0-20221216143356-66ceba885ebc, 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/infobloxopen/go-trees should I use?
v0.0.0-20221216143356-66ceba885ebc 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/infobloxopen/go-trees have?
0 vulnerabilities are recorded for github.com/infobloxopen/go-trees 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/infobloxopen/go-trees vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/infobloxopen/go-trees 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/infobloxopen/go-trees 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/infobloxopen/go-trees for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/infobloxopen/go-trees version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.