devtestudinidae

DevTestudinidae

Independent developer writing practical notes on AI-assisted development, automation, troubleshooting, and small web tools.

Space Atlas now has a security-reporting route

한국어판: Space Atlas에 보안 제보 경로를 추가했다

I added an RFC 9116 security.txt file and a SECURITY.md policy to Space Atlas. They identify the first contact and explain what reporters should leave out of a public issue. The live reporting endpoint returned HTTP 200 when checked on 15 November 2026.

Original diagram of Space Atlas's live security.txt fields and the reporting sequence from a generic public contact request to a privately arranged follow-up
This diagram uses the live `security.txt` file and the repository's `SECURITY.md` policy, both checked on 15 November 2026. It does not depict an actual report or security incident.

What the public file tells a reporter

The live /.well-known/security.txt file contains these fields:

# Report only a generic contact request in a public issue, never exploit details.
Contact: https://github.com/saramjh/space_atlas_student/issues/new
Expires: 2027-05-01T00:00:00Z
Canonical: https://spaceatlasedu.org/.well-known/security.txt
Policy: https://github.com/saramjh/space_atlas_student/blob/main/SECURITY.md
Preferred-Languages: en, ko

Contact points to a new GitHub issue. Expires sets the file’s expiry date to 1 May 2027. Canonical identifies the canonical file URL, while Policy links to the reporting instructions. Preferred-Languages lists English and Korean.

Keep the public request generic

The SECURITY.md policy asks reporters to title the issue Private security contact request and include only a generic contact request. It says not to publish exploitation steps, vulnerable URLs containing secrets, credentials, student personal information or other sensitive details in the public issue.

The maintainer can arrange a private follow-up channel before receiving confidential technical details. The project does not offer a vulnerability-bounty program. Reporters are also asked not to access, alter or expose other visitors’ data.

Static build and regression checks

PR #10 updates the build to copy .well-known into the public output and create .nojekyll there. This lets GitHub Pages serve the hidden path without processing it through Jekyll.

The regression check verifies that security.txt exists in the output, that its Contact, Expires, Canonical and Policy fields are present, and that .nojekyll was created. The same PR sets CI’s SITE_BASE to the root of the spaceatlasedu.org custom domain, replacing the old project-site prefix.

PR #10 was merged on 9 November 2026. The implementation is in commit 712deb4. I checked the live endpoint on 15 November and received HTTP 200 with text/plain; charset=utf-8.

Checks for other static-site maintainers

The separate child-data review remains open. The privacy notice says that direct unsupervised use by children under 13 is not recommended while child-directed advertising and data-handling controls are under review.