jmiller
0055b7eaaf
CodeQL Security Scanning / Analyze (actions) (push) Failing after 1m14s
Repo Health / Access control (push) Successful in 1s
Standards Compliance / Secret Scanning (push) Successful in 3s
Standards Compliance / License Header Validation (push) Successful in 2s
CodeQL Security Scanning / Analyze (javascript) (push) Failing after 1m15s
Standards Compliance / Repository Structure Validation (push) Successful in 3s
Standards Compliance / Coding Standards Check (push) Failing after 4s
Standards Compliance / Version Consistency Check (push) Successful in 3s
Standards Compliance / Workflow Configuration Check (push) Failing after 3s
Standards Compliance / Documentation Quality Check (push) Successful in 3s
Standards Compliance / README Completeness Check (push) Successful in 2s
Standards Compliance / Git Repository Hygiene (push) Successful in 2s
Standards Compliance / Line Length Check (push) Failing after 2s
Standards Compliance / Script Integrity Validation (push) Successful in 4s
Standards Compliance / File Naming Standards (push) Successful in 3s
Standards Compliance / Insecure Code Pattern Detection (push) Successful in 2s
Standards Compliance / Code Complexity Analysis (push) Successful in 4s
Standards Compliance / Code Duplication Detection (push) Successful in 4s
Standards Compliance / File Size Limits (push) Successful in 2s
Standards Compliance / Dead Code Detection (push) Successful in 3s
Standards Compliance / TODO/FIXME Tracking (push) Successful in 3s
Standards Compliance / Binary File Detection (push) Successful in 4s
Standards Compliance / Dependency Vulnerability Scanning (push) Successful in 4s
Standards Compliance / Broken Link Detection (push) Successful in 4s
Standards Compliance / Unused Dependencies Check (push) Successful in 7s
Standards Compliance / API Documentation Coverage (push) Successful in 2s
Standards Compliance / Accessibility Check (push) Successful in 3s
Standards Compliance / Performance Metrics (push) Successful in 2s
Standards Compliance / Enterprise Readiness Check (push) Successful in 4s
Standards Compliance / Repository Health Check (push) Successful in 4s
Standards Compliance / Terraform Configuration Validation (push) Successful in 6s
Repo Health / Release configuration (push) Failing after 3s
Repo Health / Scripts governance (push) Successful in 3s
Repo Health / Repository health (push) Failing after 4s
CodeQL Security Scanning / Security Scan Summary (push) Successful in 1s
Standards Compliance / Compliance Summary (push) Successful in 1s
Auto-Assign Issues & PRs / Assign unassigned issues and PRs (push) Successful in 1s
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Code of Conduct
This Code of Conduct establishes expectations for behavior within the MokoOnyx project community. The objective is to maintain a professional, inclusive, and respectful environment aligned with open source governance best practices.
Scope
This Code of Conduct applies to all project spaces, including:
- GitHub repositories, issues, pull requests, discussions, and security advisories.
- Project documentation, workflows, and release processes.
- Any communication channels officially associated with the project.
Our Standards
Participants are expected to:
- Communicate professionally and respectfully.
- Provide constructive feedback focused on technical merit and project objectives.
- Respect differing viewpoints, experience levels, and backgrounds.
- Follow documented contribution, security, and governance policies.
Unacceptable behavior includes:
- Harassment, discrimination, or exclusionary conduct.
- Personal attacks, insults, or inflammatory comments.
- Publishing private information without consent.
- Disruptive behavior that materially interferes with project operations.
Enforcement Responsibilities
Project maintainers are responsible for:
- Clarifying standards when questions arise.
- Taking appropriate and proportionate corrective action when violations occur.
- Maintaining confidentiality to the extent practical during investigations.
Reporting
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported through:
- Email:
hello@mokoconsulting.techwith subjectCODE OF CONDUCT: MokoOnyx.
Reports should include relevant context, links, screenshots, or other supporting information.
Enforcement Guidelines
Corrective actions may include, but are not limited to:
- Private warning or request for corrective action.
- Temporary or permanent restriction from project participation.
- Removal of content that violates this Code of Conduct.
Decisions are made based on impact, severity, and pattern of behavior.
No Retaliation
Retaliation against individuals who report concerns in good faith is not tolerated. Any retaliatory behavior will be treated as a separate violation.
Jurisdiction
This project is managed from Tennessee, USA. This statement is informational and does not constitute legal advice.
Metadata
- Document: CODE_OF_CONDUCT.md
- Repository: https://git.mokoconsulting.tech/MokoConsulting/MokoOnyx
- Path: /CODE_OF_CONDUCT.md
- Owner: Moko Consulting
- Version: 03.06.00
- Status: Active
- Effective Date: 2025-12-18
- Last Reviewed: 2025-12-18
Revision History
| Date | Change Summary | Author |
|---|---|---|
| 2025-12-18 | Initial publication of contributor conduct standards and enforcement process. | Moko Consulting |