All issues

Search results

Devise a way to identify withdrawn advisories

Status: Open.

#2357 In aboutcode-org/vulnerablecode;

· TG1999 opened on Jun 26, 2026

Prepare for VCIO release

Status: Open.

#2342 In aboutcode-org/vulnerablecode;

· TG1999 opened on Jun 12, 2026

Decide what info we need to store on a grouped advisory

Status: Open.

#2341 In aboutcode-org/vulnerablecode;

· TG1999 opened on Jun 12, 2026

Consider removing PYSEC importer and keep PYPA importer only

Status: Open.

#2327 In aboutcode-org/vulnerablecode;

· TG1999 opened on Jun 4, 2026

Make git clone based pipelines faster

Status: Open.

#2317 In aboutcode-org/vulnerablecode;

· TG1999 opened on May 27, 2026

Create improver to go through advisory references and create Patches or PackageCommitPatches

Status: Open.

#2302 In aboutcode-org/vulnerablecode;

· TG1999 opened on May 12, 2026

Plans to make V3 API more efficient

Status: Open.

#2271 In aboutcode-org/vulnerablecode;

· TG1999 opened on Apr 15, 2026

Write a pipeline that import data from security-advisories

Status: Open.

#2266 In aboutcode-org/vulnerablecode;

· TG1999 opened on Apr 13, 2026

NVDR: Create API endpoints to get all vulnerable and non vulnerable versions for a base package

Status: Open.

#2262 In aboutcode-org/vulnerablecode;

· TG1999 opened on Apr 10, 2026

Manage backups for VCIO

Status: Open.

#2261 In aboutcode-org/vulnerablecode;

· TG1999 opened on Apr 10, 2026

Unfurl version ranges with impacted packages at time of import

Status: Open.

#2250 In aboutcode-org/vulnerablecode;

· TG1999 opened on Apr 3, 2026

Enhance advisory grouping mechanism

Status: Open.

#2172 In aboutcode-org/vulnerablecode;

· TG1999 opened on Feb 16, 2026