msys2 / msys2/msys2-devtools

Validate CPEs somehow

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

Nobody has claimed this yet.

Dominant language
Python
Stars
9
Forks
6
PR merge metrics
No merged PRs in 30d

Description

sqlite3 -noheader "$(grype db status -o json | jq -r '.path')" \
  "SELECT json_group_array(json_object(
     'vendor', vendor,
     'product', product))
   FROM (
     SELECT DISTINCT
       vendor,
       product
     FROM cpes
     WHERE part = 'a'
     ORDER BY vendor, product
   );" | jq \
  > cpe_min.json

This gives all CPEs grype knows about. It might make sense to store this somewhere so we can lint the CPEs we use. I don't know how good the grype coverage is though.

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.

Research direction

Start by running the provided grype, sqlite3, and jq command to inspect the available CPE vendor/product data and its coverage. Determine where the project's CPEs are stored and how validation could be integrated; done means the project can lint its CPEs against a maintained data source with coverage limitations understood.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, shell, sqlite
Domain
security, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.