digitalbazaar / digitalbazaar/github-workflow-shared-action-osv-scanner
Clarify developer guidance.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- Avg merge
- 7m
- Merged PRs (30d)
- 15
Description
Summary of a comment elsewhere:
The top of the output should be clear: "The following packages have high/critical vulnerabilities and need to be updated: X, Y, Z" <-- the current output requires an enormous amount of developer effort to scan through a wall of text to try to figure out if they need to do anything at all. One line at the top should give clear guidance to developers. They should be able to take action based solely on that one line. Everything else should be in a details object [...]
Contributor guide
No contributing guide indexed for this repository
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
Start by locating how the shared OSV Scanner GitHub Action constructs its current vulnerability output. Update the output so its first line identifies high or critical vulnerable packages and gives actionable guidance, while the remaining information is kept in a details object; verify that developers can act from the first line alone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100