Vulnerability Database · Go · Package report

github.com/facebookincubator/nvdtools: vulnerability history, versions and safety

github.com/facebookincubator/nvdtools is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/facebookincubator/nvdtools v0.1.5 i

Updated on 23 Oct 2026

Good news: v0.1.5, the version you would install today, has no known vulnerabilities.

Package health score 54/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Quiet

What to do: Stay on v0.1.5 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.1.5 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 465 i
  • OpenSSF scorecard 4/10 i
  • Last release 54 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/facebookincubator/nvdtools, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.1.6-0.20231010102659-d14ce526f176 10 Oct 2023 none Apache-2.0 — Details →
v0.1.6-0.20230612062812-070f4ce499c0 12 Jun 2023 none Apache-2.0 — Details →
v0.1.6-0.20230515202602-58af2ab0f9c4 15 May 2023 none Apache-2.0 — Details →
v0.1.6-0.20230214174355-c0d18738cde5 14 Feb 2023 none Apache-2.0 — Details →
v0.1.6-0.20230126143551-a1fa51ef2a65 26 Jan 2023 none Apache-2.0 — Details →
v0.1.6-0.20221222105544-9b28e1273b3f 22 Dec 2022 none Apache-2.0 — Details →
v0.1.6-0.20221214115137-adaf938e3693 14 Dec 2022 none Apache-2.0 — Details →
v0.1.6-0.20221213045417-49e6cdb647f5 13 Dec 2022 none Apache-2.0 — Details →
v0.1.6-0.20221125170742-1bf473a3eb7e 25 Nov 2022 none Apache-2.0 — Details →
v0.1.6-0.20221010151659-7280ba547acb 10 Oct 2022 none Apache-2.0 — Details →
v0.1.6-0.20221001141149-21db753766e3 01 Oct 2022 none Apache-2.0 — Details →
v0.1.6-0.20220719140853-1903161849b5 19 Jul 2022 none Apache-2.0 — Details →
v0.1.6-0.20220629221920-70c91dcb7410 29 Jun 2022 none Apache-2.0 — Details →
v0.1.5 11 Apr 2022 none Apache-2.0 — Details →
v0.1.5-0.20220411160639-22daa55f30c8 11 Apr 2022 none Apache-2.0 — Details →
v0.1.5-0.20220411152305-765883ca9d09 11 Apr 2022 none Apache-2.0 — Details →
v0.1.5-0.20211231161522-d3c1402e869c 31 Dec 2021 none Apache-2.0 — Details →
v0.1.5-0.20211229131312-12491f271814 29 Dec 2021 none Apache-2.0 — Details →
v0.1.5-0.20210924102748-e3af1166b05d 24 Sep 2021 none Apache-2.0 — Details →
v0.1.5-0.20210706094410-952d0696a199 06 Jul 2021 none Apache-2.0 — Details →
v0.1.5-0.20210506150921-c3579d012178 06 May 2021 none Apache-2.0 — Details →
v0.1.5-0.20210504134937-36f49c6d302b 04 May 2021 none Apache-2.0 — Details →
v0.1.5-0.20210416071229-263c35b9cb66 16 Apr 2021 none Apache-2.0 — Details →
v0.1.5-0.20210330162127-11a54c9a3c01 30 Mar 2021 none Apache-2.0 — Details →
v0.1.5-0.20210128162003-127947dc6ca1 28 Jan 2021 none Apache-2.0 — Details →
v0.1.5-0.20210104173750-c9219b99a9c5 04 Jan 2021 none Apache-2.0 — Details →
v0.1.5-0.20201209144320-560caa7d0340 09 Dec 2020 none Apache-2.0 — Details →
v0.1.5-0.20201202122151-543461a948f9 02 Dec 2020 none Apache-2.0 — Details →
v0.1.4 08 Aug 2020 none Apache-2.0 — Details →
v0.1.4-0.20200622182922-aed862a62ae6 22 Jun 2020 none Apache-2.0 — Details →
v0.1.4-0.20200617054328-2dc8079a0f7d 17 Jun 2020 none Apache-2.0 — Details →
v0.1.4-0.20200518094633-d7c2fc2d0d2a 18 May 2020 none Apache-2.0 — Details →
v0.1.4-0.20200305145341-4aba69cb462c 05 Mar 2020 none Apache-2.0 — Details →
v0.1.4-0.20191216194419-eefd8104f58d 16 Dec 2019 none Apache-2.0 — Details →
v0.1.4-0.20191128125406-47f113725046 28 Nov 2019 none Apache-2.0 — Details →
v0.1.4-0.20191115173344-688794c4d3a4 15 Nov 2019 none Apache-2.0 — Details →
v0.1.4-0.20191024132624-1cb041402875 24 Oct 2019 none Apache-2.0 — Details →
v0.1.4-0.20190926132518-042a4c9deef3 26 Sep 2019 none Apache-2.0 — Details →
v0.1.3 28 Apr 2019 none Apache-2.0 — Details →
v0.1.2 24 Jan 2019 none Apache-2.0 — Details →
v0.1.1 24 Jan 2019 none Apache-2.0 — Details →
v0.1.0 23 Jan 2019 none Apache-2.0 — Details →

All 42 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/facebookincubator/nvdtools

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/facebookincubator/nvdtools

Is github.com/facebookincubator/nvdtools safe to use?

Vulert has no vulnerabilities on record for github.com/facebookincubator/nvdtools 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/facebookincubator/nvdtools's Vulert package health score?

Vulert scores github.com/facebookincubator/nvdtools 54/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/facebookincubator/nvdtools affected?

No. v0.1.5, 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/facebookincubator/nvdtools should I use?

v0.1.5 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/facebookincubator/nvdtools have?

0 vulnerabilities are recorded for github.com/facebookincubator/nvdtools 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/facebookincubator/nvdtools vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/facebookincubator/nvdtools 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/facebookincubator/nvdtools 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/facebookincubator/nvdtools for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/facebookincubator/nvdtools version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.