When patching packages, design how to track modifications
@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:
- patched for a regular bug
- patched for a security vulnerability
- patched for a new or altered feature
- updated for corrected metadata (such as origin, license, dependencies)
- 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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aboutcode-org/aboutcode
-
Cross-reference OpenChain CRA Compliance ChecklistMay be free again @PaulitePavitra claimed this 41 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aboutcode-org/aboutcode#309 · 6 comments ·
-
scancode-next: Plan federated software supply chain data infrastructurePossibly taken @ziadhany claimed this 6 days ago. Openmaintainers-only
Difficulty 4/5 3-5 days Newbie friendliness 45/100
aboutcode-org/aboutcode#325 · 2 comments · 2 assignees ·
-
scancode-next: Improve documentation, review documentation issues and pull requestsPossibly taken @hesa claimed this 8 days ago. Openmaintainers-only
aboutcode-org/aboutcode#324 · 1 assignee ·
-
scancode-next: Gather requirements through interviews with key usersPossibly taken @hesa claimed this 8 days ago. Openmaintainers-only
Difficulty 5/5 Over a week Newbie friendliness 25/100
aboutcode-org/aboutcode#323 · 1 assignee ·
-
scancode-next: Prepare ScanCode and AboutCode workshopsPossibly taken @adaaaam claimed this 6 days ago. Openmaintainers-only
aboutcode-org/aboutcode#322 · 1 assignee ·
All issues in aboutcode-org/aboutcode
Similar issues
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elastic/kibana#306401 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
agentes-chat/agentes-chat#927 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100