Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Can build tags be supported as part of version ranges for fix present or not?

Open
#232 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start by reading the linked advisory-database issue 103 and comparing how this database and OSV represent version ranges. Determine whether Python wheel build tags can be expressed in the existing advisory model; done requires a documented decision and, if supported, a defined representation and validation path.

Written by the indexing model from the issue text.

Description

at times one can re-vendor a newer shared library dependency to effectively address a CVE. In such cases one can increase a build number; whilst keeping the wheel version the same.

Some of this was already touched in https://github.com/pypa/advisory-database/issues/103

I wonder if the database here or in osv can support build tags as part of the version stream?

Dominant language
Shell
Stars
373
Forks
113
Avg merge
1d 44m
Merged PRs (30d)
8

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pypa/advisory-database

All issues in pypa/advisory-database

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.