Repository navigation
Add RFC 9116 security.txt for docs.privacycommand.privacykey.org - #13
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Deploying with
|
| 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs.privacycommand.privacykey.org had no security.txt (RFC 9116 scopes the file to its exact host). This adds a root
.well-known/security.txtand extendsnpm run buildso it reachesdist/, the same way.assetsignoredoes.New
.well-known/security.txt(field lines; the file also carries explanatory comments):PolicyandAcknowledgmentsuse 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):package.jsonbuild script, inserted after the existingcp .assetsignore dist/.assetsignore:Verified by running
npm run buildon this branch with Node 26 (mint@latestexport succeeds):dist/.well-known/security.txtis byte-identical to the source,dist/_headersis present, andnpm run checkstill 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