Public Repositories

Public vs Private Repository

Use the links below as a guide to support decision making in relation to code in the open principles and private vs public repository visibility practices.

• Code in the Open Developer Checklist – Checklist for developers when working with public repositories.

• Pre-release Code Checklist – Steps to validate code is suitable to be released into a public repository.

Vulnerability reporting

A SECURITY.md file defines a projects vulnerability reporting process, giving researchers a private, responsible disclosure channel instead of public issue trackers. It sets clear expectations around supported versions and response timelines, reduces exploitation risk, builds community trust, and signals security maturity — recognized natively by platforms like GitHub.

The security.md template file can be found in the link below

security.md

Use these guidelines to keep your code reliable, secure, and compliant.

This page was last reviewed on 3 February 2026. It needs to be reviewed again on 3 February 2027 by the page owner platops-build-notices .

This page was set to be reviewed before 3 February 2027 by the page owner platops-build-notices. This might mean the content is out of date.