Skip to content

Add security policy, contributing guide and issue templates - #302

Merged
bensynapse merged 1 commit into
mainfrom
repo/community-files
Oct 6, 2026
Merged

bensynapse merged 1 commit into
mainfrom
repo/community-files

Conversation

@bensynapse

Copy link
Copy Markdown
Owner

Part of finding F18 in the review. The repo had no security policy, contributing guide or templates.

  • SECURITY.md: report privately through the Security tab. It says which versions get fixes. It tells users before 5.0.10 to upgrade because of the exception-message leak. It also lists the official places for the project, since the old domains belong to someone else now.
  • CONTRIBUTING.md: setup, the checks CI runs, and how to preview the docs and run the example servers. It also says that 5.x must keep its public API.
  • Issue forms for bugs and features, with links to private security reports and the docs in config.yml. A short PR template.

These follow the jsonrpcclient files. Private vulnerability reporting is now on in the repo settings, so the Security tab link works. Secret scanning and push protection are on too.

SECURITY.md points reporters at GitHub's private vulnerability reporting
and names the official places for the project. CONTRIBUTING.md lists the
checks CI runs and how to work on the docs and examples. The issue form
links security reports and the docs. Same layout as jsonrpcclient.
@bensynapse
bensynapse enabled auto-merge October 6, 2026 01:32
@bensynapse
bensynapse merged commit 1429709 into main Oct 6, 2026
12 checks passed
@bensynapse
bensynapse deleted the repo/community-files branch October 6, 2026 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant