Skip to content

Commit 5820b82

Browse files
docs: org-wide security policy and code of conduct (#4)
SECURITY.md: the private reporting path (draft security advisory or email) and no version table that goes stale between releases; CODE_OF_CONDUCT.md: the canonical text. Same in every bedrock-python repository.
1 parent 5d81164 commit 5820b82

2 files changed

Lines changed: 16 additions & 10 deletions

File tree

CODE_OF_CONDUCT.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,8 @@ deemed inappropriate, threatening, offensive, or harmful.
3838

3939
## Scope
4040

41-
This Code of Conduct applies within all community spaces of the Bedrock Python blog and
42-
organisation, and also applies when an individual is officially representing the community
43-
in public spaces.
41+
This Code of Conduct applies within all community spaces, and also applies when
42+
an individual is officially representing the community in public spaces.
4443

4544
## Enforcement
4645

SECURITY.md

Lines changed: 14 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,19 @@
11
# Security Policy
22

3-
This repository contains only static site content (Markdown, config files, GitHub Actions workflows).
4-
There is no application code, no user data, and no dependencies with a runtime attack surface.
3+
## Reporting a vulnerability
54

6-
## Reporting an issue
5+
**Please do not report security vulnerabilities via public GitHub Issues.**
76

8-
If you find a problem with the site itself — broken links, incorrect information, a workflow
9-
misconfiguration — please open a [GitHub Issue](https://github.com/bedrock-python/bedrock-python.github.io/issues).
7+
Report it privately through GitHub, by
8+
[opening a draft security advisory](https://github.com/bedrock-python/bedrock-python.github.io/security/advisories/new),
9+
or send an email to **shalaevad.alexey@gmail.com**. Either way, include:
1010

11-
For security concerns related to the **libraries** documented on this site, refer to the
12-
security policy of the individual library repository.
11+
- Description of the vulnerability
12+
- Steps to reproduce
13+
- Potential impact and affected versions
14+
15+
We aim to acknowledge reports within **48 hours** and provide a fix within **7 days**
16+
for critical issues.
17+
18+
Once the fix is released, we will credit you in the release notes unless you prefer
19+
to remain anonymous.

0 commit comments

Comments
 (0)