cve-list license
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
- 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.
Similar issues
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
almanac-data/climate-almanac#138 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
OceanDataTools/openrvdas#760 ·
Maintainers usually reply within 1 day
-
level/subtask type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
wazuh/wazuh-virtual-machines#1091 ·
Maintainers usually reply within 1 day
-
Python: Bug: ChatMessageContent.from_element drops AudioContent and BinaryContent into raw TextContentPossibly taken @halcyon-past claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/semantic-kernel#14824 · 1 comment ·
Maintainers usually reply within 3 days
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stack314/django-neolith#142 · 1 comment ·
Maintainers usually reply within 1 day