jmiller cbab65e9ae
Generic: Project CI / Lint & Validate (pull_request) Successful in 9s
Generic: Project CI / Tests (pull_request) Failing after 7s
Universal: PR Check / Branch Policy (pull_request) Successful in 1s
Universal: PR Check / Require Docs Update (pull_request) Has been skipped
Universal: PR Check / Wiki Update Reminder (pull_request) Has been skipped
Cascade Main -> Dev / Cascade main -> dev (push) Successful in 5s
Universal: PR Check / Secret Scan (pull_request) Successful in 5s
Universal: PR Check / Validate PR (pull_request) Failing after 5s
Generic: Standards Compliance / Secret Scanning (push) Successful in 3s
Generic: Standards Compliance / License Header Validation (push) Successful in 4s
Generic: Standards Compliance / Repository Structure Validation (push) Successful in 3s
Generic: Standards Compliance / Coding Standards Check (push) Successful in 4s
Generic: Standards Compliance / Workflow Configuration Check (push) Failing after 4s
Generic: Standards Compliance / Documentation Quality Check (push) Successful in 4s
Generic: Standards Compliance / README Completeness Check (push) Failing after 4s
Generic: Standards Compliance / Git Repository Hygiene (push) Successful in 4s
Generic: Standards Compliance / Script Integrity Validation (push) Successful in 5s
Generic: Standards Compliance / Line Length Check (push) Successful in 4s
Generic: Standards Compliance / File Naming Standards (push) Successful in 3s
Generic: Standards Compliance / Insecure Code Pattern Detection (push) Successful in 3s
Generic: Standards Compliance / Version Consistency Check (push) Successful in 40s
Generic: Standards Compliance / Dead Code Detection (push) Successful in 4s
Generic: Standards Compliance / File Size Limits (push) Successful in 2s
Generic: Standards Compliance / Binary File Detection (push) Successful in 3s
Generic: Standards Compliance / TODO/FIXME Tracking (push) Successful in 3s
Generic: Standards Compliance / Code Duplication Detection (push) Successful in 40s
Generic: Standards Compliance / Code Complexity Analysis (push) Successful in 40s
Generic: Standards Compliance / Broken Link Detection (push) Successful in 4s
Generic: Standards Compliance / API Documentation Coverage (push) Successful in 3s
Generic: Standards Compliance / Accessibility Check (push) Successful in 3s
Generic: Standards Compliance / Performance Metrics (push) Successful in 3s
Generic: Standards Compliance / Dependency Vulnerability Scanning (push) Successful in 41s
Generic: Standards Compliance / Unused Dependencies Check (push) Successful in 45s
Generic: Standards Compliance / Terraform Configuration Validation (push) Successful in 8s
Generic: Standards Compliance / Enterprise Readiness Check (push) Failing after 43s
Joomla: Metadata Validation / Validate Joomla Metadata (pull_request) Successful in 8s
Generic: Standards Compliance / Repository Health Check (push) Failing after 44s
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Universal: PR Check / Report Issues (pull_request) Has been cancelled
Generic: Standards Compliance / Compliance Summary (push) Has been cancelled
Merge pull request 'chore(ci): remove template-only sync workflows from root' (#81) from chore/remove-template-sync-leaks into main
2026-07-13 20:45:22 +00: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
Joomla 5/6 store locator package — interactive map, location search, and admin management
https://mokoconsulting.tech/support/products/mokosuitestorelocator Readme GPL-3.0
3.6 MiB
2026-07-13 09:54:29 +00:00
Languages
PHP 59.2%
Markdown 23.9%
XML 9.2%
INI 4.8%
SQL 2.5%
Other 0.4%