Skip to content

Publish SECURITY.md on GitHub Pages - #130

Open
HodlDee wants to merge 1 commit into
mainfrom
publish-security-md
Open

HodlDee wants to merge 1 commit into
mainfrom
publish-security-md

Conversation

@HodlDee

@HodlDee HodlDee commented Sep 23, 2026

Copy link
Copy Markdown
Owner

Summary

  • Copy root SECURITY.md into docs/SECURITY.md during node build/render.mjs so GitHub Pages serves it.
  • Keeps the repository-root file as the source of truth (GitHub security reporting form).

Why

https://selfcustody.ca/SECURITY.md was 404. The file already existed at repo root.

Test plan

  • CI site check passes
  • After merge + Pages deploy, curl -sI https://selfcustody.ca/SECURITY.md returns 200
  • Body matches root SECURITY.md (same reporting email / advisory link)

The policy already lived at the repository root for GitHub's reporting
form, but Pages only serves docs/, so https://selfcustody.ca/SECURITY.md
404ed. Copy the root file into docs/ on every build so the published
bytes stay identical to the source of truth.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant