-
Notifications
You must be signed in to change notification settings - Fork 0
Create SECURITY.md File for FastSecForge #2
Copy link
Copy link
Open
Labels
SecurityIssues related to security practices, vulnerabilities, security guidelines, and reporting processesIssues related to security practices, vulnerabilities, security guidelines, and reporting processesdocumentationImprovements or additions to documentationImprovements or additions to documentationgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is needed
Metadata
Metadata
Assignees
Labels
SecurityIssues related to security practices, vulnerabilities, security guidelines, and reporting processesIssues related to security practices, vulnerabilities, security guidelines, and reporting processesdocumentationImprovements or additions to documentationImprovements or additions to documentationgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is needed
📚 Objective:
Add a SECURITY.md file to define the security policies for FastSecForge, like how to report vulnerabilities and what users/contributors should know about security practices.
✍️ Details:
Create a new file named SECURITY.md at the root of the repository.
Include basic information about:
How users can report security vulnerabilities (email or GitHub Security Advisories).
A brief note that FastSecForge aims to integrate common security practices automatically.
Mention that issues should not be posted publicly if they involve real vulnerabilities—only through private reporting.
You can refer to GitHub’s standard guidelines: https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-security-vulnerabilities
📋 Checklist:
Create SECURITY.md file.
Add reporting instructions.
Mention responsible disclosure guidelines.
Briefly list the focus areas (like secure authentication, input validation, etc.).
Link it in README.md once added.