Add enabling vulnerability reporting as a plugin hosting expectation

Open

#2 opened on Jul 28, 2024 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation

Dominant language: HTML
Stars: 4
Forks: 2
PR merge metrics: No merged PRs in 30d

Description

We would like to have a unified approach for security matters reporting. See the discussion in https://github.com/GradleUp/.github/pull/1#discussion_r1690379896

References

https://docs.github.com/en/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository

Contributor guide

Open the contributing 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

Start by reading the linked discussion in GradleUp/.github and the GitHub documentation on configuring private vulnerability reporting. Determine the unified reporting expectation for hosted plugins and document or enable that expectation across the relevant hosting guidance; done means the approach is explicit and consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack: github
Domain: documentation, security
Issue type: Documentation
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Stale
Clarity: Needs clarification
Newbie friendliness: 25/100

A short digest of beginner-friendly GitHub issues.