Skip to content

Add CONTRIBUTING and SECURITY policy - #1

Merged
tanyaroosta merged 2 commits into
mainfrom
docs/add-contributing-security
Aug 6, 2026
Merged

tanyaroosta merged 2 commits into
mainfrom
docs/add-contributing-security

Conversation

@tanyaroosta

Copy link
Copy Markdown
Collaborator

Summary

Adds two community-health / OSS-readiness files flagged as missing on this public repo:

  • CONTRIBUTING.md - how to report issues, set up a dev environment (pip install -e .), branch/PR workflow, DCO sign-off (git commit --trailer "Co-authored-by: Cursor <cursoragent@cursor.com>" -s), coding guidelines, and licensing of contributions (Apache-2.0).
  • SECURITY.md - how to privately report vulnerabilities via GitHub Private Vulnerability Reporting (and AMD PSIRT), what to include, response commitments, and supported versions.

Both are tailored to primus-mllog (ROCm Primus / MLPerf logging) and reference the existing .github/CODEOWNERS and LICENSE.

Notes

  • No code changes; docs only.
  • Consider also enabling Private Vulnerability Reporting under Settings -> Advanced Security so the SECURITY.md "Report a vulnerability" flow is active.

Test plan

  • Confirm both files render correctly on GitHub.
  • Verify Insights -> Community Standards now shows Contributing and Security policy as satisfied.

Made with Cursor

@tanyaroosta
tanyaroosta merged commit 4d31f1f into main Aug 6, 2026
2 checks passed
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