Standards
OpenForge standards define verifiable engineering outcomes rather than prescribing a single implementation. Projects choose technologies and controls that fit their environment and threat model.
Foundation
- Repository Standard
- Documentation Standard
- GitHub Standard
- Development Standard
- Engineering Tooling Standard
- Engineering Tooling Matrix
- CI/CD Standard
- Release Standard
- Internationalization Standard
- OSS Compliance Standard
Change & Compatibility
Dependency, runtime, and toolchain changes are treated as workflow-wide impact-analysis events. A newer release is not adopted merely because it is newer; compatibility, operational impact, and verification are considered together.
Security & Supply Chain
- Security Standard
- Supply Chain Security Standard
- Package & Artifact Identity
- Plugin Supply-Chain Intake Standard
- CI/CD Security Standard
- CI/CD Resilience Standard
- Developer Environment Security
- AI-Assisted Engineering Security
- Container, Kubernetes & IaC Security
- Secrets & Machine Identity
- Vulnerability Management
- Security & Incident Response
- Release Security
- Security Exceptions & Waivers
Governance & Evidence
The metrics score practical maturity across documentation, architecture, GitHub, CI/CD, security, supply chain, change management, upgrade/compatibility, developer environment, AI-assisted engineering, release, resilience, configuration, and localization.
Authoritative Source
The authoritative standards are maintained in docs/ in the OpenForge repository.
This portal explains the purpose, adoption context, trade-offs, and evidence associated with those standards in real OSS projects.