This repository provides the central entry point to The Lupaxa Project. It introduces the ecosystem, links to organisation-wide documentation, and defines the shared standards that apply across all Lupaxa organisations and repositories.
These resources ensure consistent, secure, and maintainable practices across the entire project portfolio.
These core policies and standards are maintained in dedicated repositories:
| Document | Purpose |
|---|---|
| Code of Conduct | Expected behaviour and reporting processes. |
| How to Contribute | Development workflow, review standards, coding practices. |
| Governance | How decisions are made and roles are defined. |
| Maintainers | Responsibilities, accountability, project ownership. |
| Projects Overview | Structure of the ecosystem and how repositories are grouped. |
| Security Policy | Vulnerability disclosure, secure development practices. |
| Support Guide | Where to get help and what maintainers can provide. |
These documents apply to all parts of The Lupaxa Project ecosystem.
This repository:
- Presents the organisation to contributors and users
- Acts as the root directory for global information
- Ensures that all Lupaxa organisations link to the same standards
- Supports editors, maintainers, and automation workflows
Individual repositories may include local overrides or additions — but should always reference these global standards where appropriate.
We maintain a consistent label taxonomy across the ecosystem for:
- Impact classification
- Resolution state
- Issue lifecycle
- Feature and bug types
- Dependency management and automation
These conventions improve triage, reporting clarity, and long-term maintainability.
Details are documented in the central contributing guide.
Security is designed into every layer of The Lupaxa Project:
- Signed commits are required for all contributions
- Workflows operate with least privilege by default
- Reusable workflows include input validation and guardrails
- Vulnerability reporting follows a standard automated procedure
Security requirements are detailed in the central security policy.
All of The Lupaxa Project organisations follow consistent rules for:
- Code quality and review policies
- Documentation expectations
- Testing, versioning, and release processes
- Lifecycle management for features, issues, and repositories
- Automation safety and permissions
These principles ensure predictability, fairness, and technical excellence across the entire project.
We welcome contributions from anyone aligned with the values of The Lupaxa Project.
Before contributing, please review:
All contributions must follow the organisation-wide requirements.
Please do not report vulnerabilities publicly.
Refer to the Security Policy for responsible disclosure instructions.
Unless a repository states otherwise, code under The Lupaxa Project follows the MIT License.
© The Lupaxa Project.
Where exploration meets precision.
Where the untamed meets the engineered.