Consider adding PURL

Open
#51 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
tooling

Research direction

Start by reading the package-notes code that handles existing package-identification metadata, then study the linked PURL specification and compare it with the project's current CPE approach. The issue does not name files or tests; completion would require an agreed scope for PURL support and corresponding implementation and validation.

Written by the indexing model from the issue text.

Description

Package URL is a SPDX specification for identifying packages and upstream releases. I'm not really sure if it replaces CPE completely, as CPE is capable of generally describing software artifacts. But it would probably be a good idea for package-notes to support PURL.

https://github.com/package-url/purl-spec

Dominant language
Python
Stars
28
Forks
15
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 systemd/package-notes

All issues in systemd/package-notes

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.