Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions apps/dashboard/public/.well-known/security.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
Contact: mailto:security@databuddy.cc
Policy: https://github.com/databuddy-analytics/Databuddy/blob/main/SECURITY.md
Canonical: https://databuddy.cc/.well-known/security.txt
Expires: 2027-04-10T00:00:00.000Z
Preferred-Languages: en
Comment on lines +1 to +5
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 File won't be served at /.well-known/security.txt

Placing this file at the repository root does not make it accessible via HTTP. In this monorepo, the Next.js dashboard serves static files from apps/dashboard/public/ — a file needs to live there (and/or in apps/docs/public/) for it to be reachable at https://[domain]/.well-known/security.txt. Without that, the file exists only in version control and no automated scanner or security researcher will actually find it, defeating the RFC 9116 goal entirely.

Move the file to the correct public directory of whichever app owns the primary domain:

apps/dashboard/public/.well-known/security.txt
apps/docs/public/.well-known/security.txt   # if docs is the main public domain

Comment on lines +1 to +5
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 PR targets main instead of staging

The project's CLAUDE.md guidelines specify that PRs should be opened against staging, not main. This PR targets main directly. Consider retargeting to staging per the contribution guidelines.