Add a security policy and three issue templates - #7
Merged
Conversation
Staged as patches/DiffBio/2026-08-27-005-community-files in avitai-portfolio. Applied against 1ea84a3.
mahdi-shafiei
changed the title
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.
Add a security policyand three issue templates
What
Adds
SECURITY.md, plusbug_report.yml,feature_request.ymlandconfig.ymlunder.github/ISSUE_TEMPLATE/.Both are adapted from calibrax, which is the only one of the five repositories with a
complete community-file set. The security scope section is rewritten for this project
rather than copied, and the templates carry this project's name and version field.
Why
The launch READMEs were reframed to invite issues, questions and pull requests as the
main call to action. Four of the five repositories render a Security badge on the first
screen and have no security policy telling a reporter where to send anything they find,
and three have no issue templates for the issues the README asks for.
This is the gap between asking for contributions and being ready to receive them.
Verification
Every template parses as YAML. The repository name substitution was checked in both directions: no occurrence of calibrax survives in these files, and the project's own name appears in each template.
What this does not close
avitai-portfolio-2026-08-27-003stays open. It also records missingCONTRIBUTING.mdand
CODE_OF_CONDUCT.md, neither of which is in this patch.security@avitai.biois taken from calibrax's already-published policy. Confirm itactually receives mail before merging, since a security policy pointing at a dead address
is worse than none.