cve-list license

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

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

The request is a licensing question, not a code change: the repository root has no LICENSE file, and the issue asks maintainers to confirm the BSD-3-Clause intent from the Raspberry Pi licensing page and to state the terms of the OSV feed at downloads.raspberrypi.com/security/osv/. Do not pick a licence on the maintainers' behalf; the first step is to check the licensing page and the feed's terms. Done means a maintainer has confirmed the licence and a LICENSE file has been added, which is a decision for the project rather than a newcomer's patch.

Written by the indexing model from the issue text.

Description

Thank you for publishing cve-list and the kernel OSV feed. We build products on Raspberry Pi OS and scan our release images for CVEs; the Pi kernel feed and the +rpt epoch cross-check solve problems we had also run into, and we'd like to use cve-list as part of our own scanning pipeline.

The repository doesn't have a LICENSE file, and the scripts don't carry licence headers. Your licensing page says most Raspberry Pi code is released under BSD-3-Clause; could you confirm that's the intent for cve-list and add a LICENSE file? It would also help to know the terms for the OSV feed at downloads.raspberrypi.com/security/osv/ (for example CC-BY-4.0, as OSV.dev uses).

If we find issues while using it, we'll report them here.

Thanks again.

:Bob Tatar

Dominant language
Python
Stars
1
Forks
2
Avg merge
11h 15m
Merged PRs (30d)
4

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.

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.