Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

SECURITY.md refresh

Open
#708 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet

Research direction

Open SECURITY.md and inspect its link to the c/common repository's security guidance. Confirm the bubblewrap-specific email or reporting channel with maintainers, then update the document so reports no longer go to Podman's mailing list; done when the new channel is clearly documented.

Written by the indexing model from the issue text.

Description

bubblewrap's SECURITY.md points to the no-longer maintained (apart from the release-* branches) c/common repo's SECURITY.md file which mentions emailing podman's security mailing list. So, podman's mailing list will end up receiving any security issues in bubblewrap.

Suggest having a separate email / reporting channel dedicated to bubblewrap.

Dominant language
C
Stars
8.9k
Forks
391
Avg merge
1d 32m
Merged PRs (30d)
7

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 containers/bubblewrap

All issues in containers/bubblewrap

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.