Update docs on guidance for reporting container Vulns

Open
#589 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker

Research direction

Start with the README Support section at the linked URL and inspect the repository’s security section. The expected customer process for sharing container vulnerability scan reports is not specified, so confirm that guidance before editing; done means the relevant section clearly explains what customers should report and how.

Written by the indexing model from the issue text.

Description

Docs should be updated to advise users on the expected way they should report and share vuln scan reports in the support section and or security section:

https://github.com/splunk/docker-splunk#support

Advise what you want the customer to do and how.

Dominant language
Python
Stars
549
Forks
277
Avg merge
3d 9h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from splunk/docker-splunk

All issues in splunk/docker-splunk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.