Jonathan Miller 86bf172c43
Repo Health / Access control (push) Failing after 2s
Standards Compliance / Secret Scanning (push) Failing after 2s
Standards Compliance / License Header Validation (push) Successful in 3s
Standards Compliance / Repository Structure Validation (push) Successful in 3s
Standards Compliance / Coding Standards Check (push) Failing after 4s
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 / File Naming Standards (push) Successful in 2s
Standards Compliance / Script Integrity Validation (push) Successful in 4s
Standards Compliance / Line Length Check (push) Failing after 3s
Standards Compliance / Insecure Code Pattern Detection (push) Successful in 3s
Standards Compliance / Dead Code Detection (push) Successful in 4s
Standards Compliance / File Size Limits (push) Successful in 2s
Standards Compliance / Binary File Detection (push) Successful in 3s
Standards Compliance / TODO/FIXME Tracking (push) Successful in 3s
Standards Compliance / Version Consistency Check (push) Successful in 50s
Standards Compliance / Code Complexity Analysis (push) Successful in 48s
Standards Compliance / Broken Link Detection (push) Successful in 4s
Standards Compliance / Code Duplication Detection (push) Successful in 52s
Standards Compliance / API Documentation Coverage (push) Successful in 3s
Standards Compliance / Accessibility Check (push) Successful in 2s
Standards Compliance / Performance Metrics (push) Successful in 2s
Standards Compliance / Dependency Vulnerability Scanning (push) Successful in 51s
Standards Compliance / Terraform Configuration Validation (push) Successful in 5s
Repo Health / Release configuration (push) Has been skipped
Repo Health / Scripts governance (push) Has been skipped
Repo Health / Repository health (push) Has been skipped
Standards Compliance / Unused Dependencies Check (push) Successful in 52s
Standards Compliance / Enterprise Readiness Check (push) Failing after 49s
Standards Compliance / Repository Health Check (push) Failing after 49s
Standards Compliance / Compliance Summary (push) Failing after 1s
fix: PR sync always runs, cleans up stale branches
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-22 04:29:48 -05:00
2026-01-08 19:49:02 -06:00
2026-01-08 19:49:02 -06:00
2026-01-08 19:49:02 -06:00
2026-04-22 04:05:54 -05:00

Code of Conduct

1. Purpose

The purpose of this Code of Conduct is to ensure a safe, inclusive, and respectful environment for all contributors and participants in Moko Consulting projects. This applies to all interactions, whether in repositories, issue trackers, documentation, meetings, or community spaces.

2. Our Standards

Participants are expected to uphold behaviors that strengthen our community, including:

Demonstrating empathy and respect toward others. Being inclusive of diverse viewpoints and backgrounds. Gracefully accepting constructive feedback. Prioritizing collaboration over conflict. Showing professionalism in all interactions.

Unacceptable behavior includes:

Harassment, discrimination, or derogatory comments. Threatening or violent language or actions. Disruptive, aggressive, or intentionally harmful behavior. Publishing others private information without permission. Any behavior that violates applicable laws.

3. Responsibilities of Maintainers

Maintainers are responsible for:

Clarifying acceptable behavior. Taking appropriate corrective action when unacceptable behavior occurs. Removing, editing, or rejecting contributions that violate this Code. Temporarily or permanently banning contributors who engage in repeated or severe violations.

4. Scope

This Code applies to:

All Moko Consulting repositories. All documentation and collaboration platforms. Public and private communication related to project activities. Any representation of Moko Consulting in online or offline spaces.

5. Enforcement

Instances of misconduct may be reported to: hello@mokoconsulting.tech

All reports will be reviewed and investigated promptly and fairly. Maintainers are obligated to maintain confidentiality where possible.

Consequences may include:

A warning. Required training or mediation. Temporary or permanent bans. Escalation to legal authorities when required.

6. Acknowledgements

This Code of Conduct is inspired by widely adopted community guidelines, including the Contributor Covenant and major open-source collaboration standards.

Governance Guide Contributor Guide Documentation Index

This Code of Conduct is a living document and may be updated following the established Change Management process.

S
Description
MokoSuiteClient is the Joomla 5.x / 6.x client-facing tracker and identity layer for the MokoSuite platform.
https://mokoconsulting.tech/support/products/mokowaas
Readme GPL-3.0
22 MiB
Languages
PHP 67.6%
Markdown 18.8%
XML 5.9%
INI 4.1%
SQL 1.1%
Other 2.4%