Skip to content

CODE_OF_CONDUCT.md

Latest commit

 

History

History
47 lines (29 loc) · 2.43 KB

CODE_OF_CONDUCT.md

File metadata and controls

47 lines (29 loc) · 2.43 KB
Raw

Code of Conduct

UniProof welcomes constructive participation from people with different backgrounds, experience levels, and viewpoints.

Expected conduct

Contributors and maintainers should:

  • communicate respectfully and focus criticism on ideas, code, evidence, and outcomes;
  • give actionable technical feedback without harassment, insults, threats, or personal attacks;
  • respect privacy and never expose another person's credentials, private communications, academic records, identity documents, or other sensitive data;
  • avoid discriminatory, sexual, intimidating, or deliberately disruptive behavior;
  • respect project scope, security boundaries, licenses, and attribution requirements;
  • correct mistakes transparently when evidence shows that a prior claim or implementation was wrong.

Unacceptable conduct

Examples include:

  • harassment, discriminatory language, stalking, threats, or unwanted sexual attention;
  • publishing private information without permission;
  • deliberately introducing or concealing malware, credential theft, destructive behavior, or data exfiltration;
  • knowingly fabricating test results, citations, security evidence, benchmark results, or implementation status;
  • using project spaces primarily for spam or unrelated promotion;
  • repeated bad-faith disruption after a maintainer has asked for behavior to stop.

Project spaces

This policy applies to repository issues, pull requests, discussions, reviews, commits, documentation, and other spaces directly associated with UniProof.

Technical disagreement is expected. Strong criticism of a design or patch is acceptable when it remains specific, evidence-based, and directed at the work rather than the person.

Reporting conduct concerns

Report conduct concerns privately to the repository owner through an available private GitHub/contact channel. Do not publish sensitive evidence in a public issue.

Security vulnerabilities and exposed credentials are handled separately under SECURITY.md.

Enforcement

The repository owner may edit or remove abusive content, close discussions, reject contributions, restrict participation, or block contributors when necessary to protect participants and the project.

Enforcement decisions should be proportionate to the behavior, available evidence, recurrence, and risk to others.

Attribution

This project-specific policy is intentionally concise and is not presented as an adoption of a third-party code-of-conduct text.