From a7e93fd3d958e2b07ca42725d9260a99e098edda Mon Sep 17 00:00:00 2001 From: Tushar Goel Date: Mon, 6 Jul 2026 23:56:52 +0530 Subject: [PATCH 1/4] VCIO V3 API migration completed Signed-off-by: Tushar Goel --- .../2026-07-06-vcio-v3-migration-completed.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md diff --git a/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md b/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md new file mode 100644 index 0000000..6d06102 --- /dev/null +++ b/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md @@ -0,0 +1,12 @@ +--- +slug: vcio-v3-migration-completed +title: VulnerableCode V3 API migration is completed +authors: [tg1999] +tags: [vcio, vulnerabilities, advisories, purl, api] +hide_table_of_contents: false +--- + +# VulnerableCode API Deprecation and V3 Introduction + +The AboutCode team has deprecated the V1 and V2 API of VulnerableCode (public.vulnerablecode.io) with the latest release of v40.0.0 https://github.com/aboutcode-org/vulnerablecode/releases/tag/v40.0.0 and https://github.com/aboutcode-org/vulnerablecode/releases/tag/vcio-v1 this is tag with the last data +dump of V1 and V2 API format. You can refer to announcement of deprecation blog to understand why V3 format is a more helpful format moving forward. [Blog](../vcio-migration-announcement-aboutcode/2026-01-21-vcio-migration-announcement-aboutcode.md) From c591c43571a3ca8f2e0dd6c3c554b520ce58a579 Mon Sep 17 00:00:00 2001 From: Tushar Goel Date: Tue, 7 Jul 2026 00:01:16 +0530 Subject: [PATCH 2/4] fix typo Signed-off-by: Tushar Goel --- .../2026-07-06-vcio-v3-migration-completed.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md b/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md index 6d06102..4b8d072 100644 --- a/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md +++ b/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md @@ -8,5 +8,5 @@ hide_table_of_contents: false # VulnerableCode API Deprecation and V3 Introduction -The AboutCode team has deprecated the V1 and V2 API of VulnerableCode (public.vulnerablecode.io) with the latest release of v40.0.0 https://github.com/aboutcode-org/vulnerablecode/releases/tag/v40.0.0 and https://github.com/aboutcode-org/vulnerablecode/releases/tag/vcio-v1 this is tag with the last data +The AboutCode team has deprecated the V1 and V2 API of VulnerableCode (public.vulnerablecode.io) with the latest release of v40.0.0 https://github.com/aboutcode-org/vulnerablecode/releases/tag/v40.0.0 and https://github.com/aboutcode-org/vulnerablecode/releases/tag/vcio-v1 this is the tag with the last data dump of V1 and V2 API format. You can refer to announcement of deprecation blog to understand why V3 format is a more helpful format moving forward. [Blog](../vcio-migration-announcement-aboutcode/2026-01-21-vcio-migration-announcement-aboutcode.md) From ce97488d04aa63ab422939f2d1ff94c049a51fac Mon Sep 17 00:00:00 2001 From: Tushar Goel Date: Tue, 7 Jul 2026 00:12:06 +0530 Subject: [PATCH 3/4] Add reference to use V3 API Signed-off-by: Tushar Goel --- .../2026-07-06-vcio-v3-migration-completed.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md b/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md index 4b8d072..1b5ca84 100644 --- a/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md +++ b/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md @@ -8,5 +8,9 @@ hide_table_of_contents: false # VulnerableCode API Deprecation and V3 Introduction -The AboutCode team has deprecated the V1 and V2 API of VulnerableCode (public.vulnerablecode.io) with the latest release of v40.0.0 https://github.com/aboutcode-org/vulnerablecode/releases/tag/v40.0.0 and https://github.com/aboutcode-org/vulnerablecode/releases/tag/vcio-v1 this is the tag with the last data -dump of V1 and V2 API format. You can refer to announcement of deprecation blog to understand why V3 format is a more helpful format moving forward. [Blog](../vcio-migration-announcement-aboutcode/2026-01-21-vcio-migration-announcement-aboutcode.md) +The AboutCode team has deprecated the V1 and V2 API of VulnerableCode (https://public.vulnerablecode.io) with the latest release of v40.0.0 https://github.com/aboutcode-org/vulnerablecode/releases/tag/v40.0.0 and https://github.com/aboutcode-org/vulnerablecode/releases/tag/vcio-v1 this is the tag with the last data +dump of V1 and V2 API format. + +You can refer to https://public.vulnerablecode.io/api/docs/ and https://vulnerablecode.readthedocs.io/en/latest/api_v3_usage.html to understand the latest V3 API usage. + +You can refer to announcement of deprecation blog to understand why V3 format is a more helpful format moving forward. [Blog](../vcio-migration-announcement-aboutcode/2026-01-21-vcio-migration-announcement-aboutcode.md) From a9561114f2bcb9fff54a171307401a552ebb5ff5 Mon Sep 17 00:00:00 2001 From: Tushar Goel Date: Wed, 8 Jul 2026 00:11:21 +0530 Subject: [PATCH 4/4] Address review comments Signed-off-by: Tushar Goel --- .../2026-07-06-vcio-v3-migration-completed.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md b/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md index 1b5ca84..9da6d7a 100644 --- a/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md +++ b/website/blog/vcio-v3-migration-completed/2026-07-06-vcio-v3-migration-completed.md @@ -8,9 +8,8 @@ hide_table_of_contents: false # VulnerableCode API Deprecation and V3 Introduction -The AboutCode team has deprecated the V1 and V2 API of VulnerableCode (https://public.vulnerablecode.io) with the latest release of v40.0.0 https://github.com/aboutcode-org/vulnerablecode/releases/tag/v40.0.0 and https://github.com/aboutcode-org/vulnerablecode/releases/tag/vcio-v1 this is the tag with the last data -dump of V1 and V2 API format. +The AboutCode team has released v40.0.0 https://github.com/aboutcode-org/vulnerablecode/releases/tag/v40.0.0 with the the V3 VulnerableCode API which replaces "vulnerabilities" with "advisories". Prior to this release we reported vulnerabilities for each PURL (Package-URL) where a vulnerability combined multiple advisories. With the new advisory model each advisory is reported individually which provides more granular data and makes it easier for you to prioritize data sources that you trust more. -You can refer to https://public.vulnerablecode.io/api/docs/ and https://vulnerablecode.readthedocs.io/en/latest/api_v3_usage.html to understand the latest V3 API usage. +With this release the VulnerableCode V1 and V2 APIs have been deprecated along with the corresponding vulnerability-based data. You can download the V1/V2 vulnerability data from: https://github.com/aboutcode-org/vulnerablecode/releases/tag/vcio-v1. This is a final data archive for the old data structure. -You can refer to announcement of deprecation blog to understand why V3 format is a more helpful format moving forward. [Blog](../vcio-migration-announcement-aboutcode/2026-01-21-vcio-migration-announcement-aboutcode.md) +Refer to https://public.vulnerablecode.io/api/docs/ and https://vulnerablecode.readthedocs.io/en/latest/api_v3_usage.html to understand the latest V3 API usage.