Vulnerability Database · Go · Package report

github.com/microsoft/azure-devops-go-api/azuredevops: vulnerability history, versions and safety

github.com/microsoft/azure-devops-go-api/azuredevops 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/microsoft/azure-devops-go-api/azuredevops v1.0.0-b5 i

Updated on 23 Oct 2026

Good news: v1.0.0-b5, 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 v1.0.0-b5 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.0-b5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v1.0.0-b5 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 224 i
  • OpenSSF scorecard 4/10 i
  • Last release 73 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/microsoft/azure-devops-go-api/azuredevops, 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
v1.0.0-b5.0.20260610092110-dd0480f058d6 10 Jun 2026 none MIT — Details →
v0.0.0-20241014080628-3045bdf43455 14 Oct 2024 none MIT — Details →
v1.0.0-b5.0.20241014080628-3045bdf43455 14 Oct 2024 none MIT — Details →
v1.0.0-b5.0.20240926091924-25121328f453 26 Sep 2024 none MIT — Details →
v1.0.0-b5.0.20240924152801-bf71b21aa583 24 Sep 2024 none MIT — Details →
v1.0.0-b5.0.20240917152219-cf72222764ec 17 Sep 2024 none MIT — Details →
v1.0.0-b5.0.20240826115726-670a90d0787e 26 Aug 2024 none MIT — Details →
v1.0.0-b5.0.20240823141332-9296dca521a3 23 Aug 2024 none MIT — Details →
v0.0.0-20240822154302-79666e531cdd 22 Aug 2024 none MIT — Details →
v1.0.0-b3.0.20240822154302-79666e531cdd 22 Aug 2024 none MIT — Details →
v1.0.0-b5.0.20240822144150-2a2e14eb5a0c 22 Aug 2024 none MIT — Details →
v0.0.0-20230914114614-c9e5fa06da2c 14 Sep 2023 none MIT — Details →
v1.0.0-b5.0.20230914114614-c9e5fa06da2c 14 Sep 2023 none MIT — Details →
v1.0.0-b5.0.20230905071550-b030a68c30ea 05 Sep 2023 none MIT — Details →
v1.0.0-b5.0.20230612182115-8dbf8bfd3346 12 Jun 2023 none MIT — Details →
v0.0.0-20230417212659-a6271be3ed02 17 Apr 2023 none MIT — Details →
v1.0.0-b5.0.20230417212659-a6271be3ed02 17 Apr 2023 none MIT — Details →
v0.0.0-20220126122445-00dac5c86739 26 Jan 2022 none MIT — Details →
v1.0.0-b5.0.20220126122445-00dac5c86739 26 Jan 2022 none MIT — Details →
v0.0.0-20211202191553-0974d0145be8 02 Dec 2021 none MIT — Details →
v1.0.0-b5.0.20211202191553-0974d0145be8 02 Dec 2021 none MIT — Details →
v1.0.0-b5.0.20211202191000-0e1d21512172 02 Dec 2021 none MIT — Details →
v1.0.0-b5.0.20211201082551-9269abbefe17 01 Dec 2021 none MIT — Details →
v0.0.0-20211126130705-9b13f230c8e1 26 Nov 2021 none MIT — Details →
v1.0.0-b5.0.20211126130705-9b13f230c8e1 26 Nov 2021 none MIT — Details →
v1.0.0-b5.0.20210805214657-56872f068f0b 05 Aug 2021 none MIT — Details →
v1.0.0-b4.0.20200823222236-09c8cad426a6 23 Aug 2020 none MIT — Details →
v1.0.0-b5 23 Aug 2020 none MIT — Details →
v1.0.0-b2.0.20200812183055-f739e5580c90 12 Aug 2020 none MIT — Details →
v1.0.0-b4 12 Aug 2020 none MIT — Details →
v1.0.0-b2.0.20200519132252-4fd403de5c92 19 May 2020 none MIT — Details →
v1.0.0-b3 19 May 2020 none MIT — Details →
v1.0.0-b1.0.20200517172011-0ae494aade32 17 May 2020 none MIT — Details →
v1.0.0-b2 17 May 2020 none MIT — Details →
v0.0.0-20200327121006-543de4815ec2 27 Mar 2020 none MIT — Details →
v1.0.0-b1 27 Mar 2020 none MIT — Details →
v0.0.0-20200311171536-17093eb5e360 11 Mar 2020 none MIT — Details →
v0.0.0-20191230214132-3cd87c562d09 30 Dec 2019 none MIT — Details →
v0.0.0-20191125191507-ad702f5ae0cd 25 Nov 2019 none MIT — Details →
v0.0.0-20191123193149-59979e61bcc4 23 Nov 2019 none MIT — Details →
v0.0.0-20191018194956-273e55a7119a 18 Oct 2019 none MIT — Details →
v0.0.0-20191014190507-26902c1d4325 14 Oct 2019 none MIT — Details →
v0.0.0-20191011155002-b909a25cb2ee 11 Oct 2019 none MIT — Details →
v0.0.0-20191011124754-fcd30e85c57f 11 Oct 2019 none MIT — Details →
v0.0.0-20191008140207-e35debc23688 08 Oct 2019 none MIT — Details →
v0.0.0-20190912142452-3207b4a469d3 12 Sep 2019 none MIT — Details →
v0.0.0-20190903225844-47715c5e3aa1 03 Sep 2019 none MIT — Details →
v0.0.0-20190822161802-a196ec51000e 22 Aug 2019 none MIT — Details →

All 48 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/microsoft/azure-devops-go-api/azuredevops

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/microsoft/azure-devops-go-api/azuredevops

Is github.com/microsoft/azure-devops-go-api/azuredevops safe to use?

Vulert has no vulnerabilities on record for github.com/microsoft/azure-devops-go-api/azuredevops 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/microsoft/azure-devops-go-api/azuredevops's Vulert package health score?

Vulert scores github.com/microsoft/azure-devops-go-api/azuredevops 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/microsoft/azure-devops-go-api/azuredevops affected?

No. v1.0.0-b5, 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/microsoft/azure-devops-go-api/azuredevops should I use?

v1.0.0-b5 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/microsoft/azure-devops-go-api/azuredevops have?

0 vulnerabilities are recorded for github.com/microsoft/azure-devops-go-api/azuredevops 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/microsoft/azure-devops-go-api/azuredevops vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/microsoft/azure-devops-go-api/azuredevops 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/microsoft/azure-devops-go-api/azuredevops 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/microsoft/azure-devops-go-api/azuredevops for upcoming vulnerabilities?

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