docs: add Code of Conduct and Security policy#30
Merged
Conversation
Add CODE_OF_CONDUCT.md (Contributor Covenant 2.1, verbatim; enforcement contact is an interim pointer to the maintainer until a dedicated community channel exists) and SECURITY.md (private vulnerability reporting via GitHub's Security tab, project-specific scope, pre-1.0 supported versions). Closes out the Phase 1 community files.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The last two Phase 1 community files.
CODE_OF_CONDUCT.md— Contributor Covenant 2.1,reproduced verbatim. The one substituted field is the enforcement contact: an interim pointer
to the maintainer (@adworzynski), to be replaced by a
dedicated community channel (e.g. a moderated chat) when one exists.
SECURITY.md— report privately via GitHub's Security → "Report a vulnerability"(private vulnerability reporting), no email exposed. Includes a project-specific scope
(path-escape / write-guard bypass / code-execution-from-data / validation-or-determinism escape)
and a pre-1.0 "latest
mainonly" support statement.Proof
Docs-only — no
src/change, no tests. The CoC body was diffed against the canonicalContributor Covenant 2.1; the only content difference is the enforcement-contact line above.
Action needed before this fully works (Phase 2, go-public)
vulnerability reporting → Enable. The "Report a vulnerability" button
SECURITY.mdpoints toonly appears once this is on (and the repo is public).