Security fixes apply to the current main branch. Historical releases may remain available for reproducibility but are not maintained independently.

Do not publish credentials, personal data or an exploitable security report in a public issue. Use GitHub's private vulnerability reporting feature from the repository Security tab when available.

Include:

• affected file, workflow or release;
• impact and reproducible steps;
• any suggested mitigation;
• whether the report contains sensitive data.

Data-quality corrections that do not create a security risk belong in the public issue forms instead.

The repository publishes static data, Python build scripts and a static GitHub Pages site. Reports about upstream data accuracy, CAP coverage or coordinates are data-quality issues unless they expose a distinct security impact.