haskell/security-advisories

How should OSV.dev consumers of Haskell Security Advisory DB records provide feedback on them?

Open

#252 opened on Nov 27, 2024

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Haskell (26 forks)auto 404
ZuriHacgood first issue

Repository metrics

Stars
 (63 stars)
PR merge metrics
 (PR metrics pending)

Description

We're seeking to shorten the feedback loop by directly connecting OSV.dev downstream consumers of Haskell vulnerabilities with the Haskell Security Advisory DB for any corrective feedback on individual records.

Could you clearly define a feedback channel (file an issue, create a PR) for downstream users to follow to be able to correct a problem with an OSV record published in the Haskell Security Advisory DB?

See https://github.com/google/osv.dev/issues/2191 for more context.

Contributor guide

Research direction
Review the linked issue for context and propose a clear feedback channel (e.g., filing an issue or creating a PR) with instructions for downstream users.
Tech stack
None
Domain
securitydocumentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80