[meta] PKG_CPE_ID and security issue tracking
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Hi,
is there any documentation for maintainers how to handle PKG_CPE_ID ? Or some idea?
@Andy2244 Pointed out in this PR https://github.com/openwrt/packages/pull/8525#issuecomment-477935436 that it would be a useful thing to have some sort of documentation with examples (and I agree with him).
Right now there are project already using this variable see https://github.com/kkreitmair/cve-indicator
Contributor 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.
Research direction
Review CONTRIBUTING.md, the discussion in PR #8525, and the referenced cve-indicator project to understand how PKG_CPE_ID is used. Document maintainer handling with concrete examples and explain how it relates to security issue tracking; the documentation should answer the question without relying on the original issue thread.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100