Skip to content

Add RFC 9116 security.txt for docs.privacycommand.privacykey.org - #13

Merged
adamXbot merged 1 commit into
mainfrom
security/security-txt-encryption
Oct 9, 2026
Merged

adamXbot merged 1 commit into
mainfrom
security/security-txt-encryption

Conversation

@adamXbot

@adamXbot adamXbot commented Oct 9, 2026

Copy link
Copy Markdown
Collaborator

docs.privacycommand.privacykey.org had no security.txt (RFC 9116 scopes the file to its exact host). This adds a root .well-known/security.txt and extends npm run build so it reaches dist/, the same way .assetsignore does.

New .well-known/security.txt (field lines; the file also carries explanatory comments):

Contact: https://github.com/privacykey/privacycommand/security/advisories/new
Contact: mailto:security@privacykey.org
Encryption: https://github.com/AdamXweb.gpg
Encryption: openpgp4fpr:54BFCE808324E569FB1919B304AAA3CBD117D9B2
Policy: https://github.com/privacykey/privacycommand/blob/main/.github/SECURITY.md
Acknowledgments: https://github.com/privacykey/privacycommand/blob/main/.github/SECURITY.md#hall-of-fame
Canonical: https://docs.privacycommand.privacykey.org/.well-known/security.txt
Preferred-Languages: en
Expires: 2027-10-01T00:00:00Z

Policy and Acknowledgments use the real path (.github/SECURITY.md; the root path 404s); that file has a "Hall of fame" heading. Note: docs.privacycommand.privacykey.org has no DNS record yet, so the Canonical URL cannot be fetched until the host is attached to the Worker.

New _headers (Workers static assets rule so the file is served as RFC 9116 requires; not served itself):

/.well-known/security.txt
  Content-Type: text/plain; charset=utf-8

package.json build script, inserted after the existing cp .assetsignore dist/.assetsignore:

cp _headers dist/_headers && mkdir -p dist/.well-known && cp -R .well-known/. dist/.well-known/

Verified by running npm run build on this branch with Node 26 (mint@latest export succeeds): dist/.well-known/security.txt is byte-identical to the source, dist/_headers is present, and npm run check still passes. Mintlify's export also picks both up on its own, so the explicit copy is the guarantee rather than the only path. Nothing deployed.

The key is the one published at https://github.com/AdamXweb.gpg (identities security@adamxweb.com and security@privacykey.org, expires 2028-10-08). Every URL in the file was checked to return 200 on 2026-10-09.

🤖 Generated with Claude Code

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
docs-privacycommand 530429a Commit Preview URL

Branch Preview URL
Oct 09 2026, 04:59 AM

@adamXbot
adamXbot merged commit f7a55bd into main Oct 9, 2026
2 checks passed
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