When patching packages, design how to track modifications

Open
#158 4 comments 0 reactions 0 assignees View on GitHub

@devansh6107 is already working on this.

Since Oct 10, 2026.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
security

Research direction

Start by reviewing the proposed tracking locations named in the issue: ABOUT files, DejaCode, and the PurlDB, then trace the downstream vulnerability and version-matching processes they would affect. Done means an agreed design can distinguish regular, security, feature, metadata, renamed, and version modifications without introducing false-positive or false-negative lookups.

Written by the indexing model from the issue text.

Description

When a package is modified locally in a codebase, we should be able track these modifications and how to identify them.

Why? Because a package may have been:

  1. patched for a regular bug
  2. patched for a security vulnerability
  3. patched for a new or altered feature
  4. updated for corrected metadata (such as origin, license, dependencies)
  5. renamed or its version changed (or not :] )

In all these cases, we may have some problems if we do not known about this:

  • we may report it as vulnerable when this is not the case
  • we may not report it as vulnerable when this is the case
  • we may match it it incorrectly to an upstream version or an altered version

Tracking could be done in ABOUT files, in DejaCode and the PurlDB and be used by downstream processes to avoid false negative and false positive lookups. This is especially important when we have renamed packages that are patched but where the original unpatched package and the patched version could be both vulnerable.

Dominant language
Batchfile
Stars
316
Forks
257
PR merge metrics
No merged PRs in 30d

Getting set up

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 aboutcode-org/aboutcode

All issues in aboutcode-org/aboutcode

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.