-
Notifications
You must be signed in to change notification settings - Fork 37
Add security.txt #262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add security.txt #262
Conversation
WalkthroughA new Changes
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
🧹 Nitpick comments (3)
static/.well-known/security.txt (3)
8-14
: Consider adding optional fields
You might enrich the policy by including sections likeAcknowledgements:
(to credit reporters) orHiring:
(to signal open roles), which are supported by the spec but not required.
12-12
: Prefer relative URLs for maintainability
SwitchingCanonical:
andSignature:
from absolute to relative paths (e.g.,/.well-known/security.txt
) can reduce update overhead if your domain changes.
1-14
: Verify web server configuration
Ensure your deployment serves thestatic/.well-known
directory under/.well-known
, so thathttps://unraid.net/.well-known/security.txt
is accessible without redirects or blocks.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
static/.well-known/security.txt
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
- GitHub Check: build
- GitHub Check: AWS Amplify Console Web Preview
🔇 Additional comments (1)
static/.well-known/security.txt (1)
1-7
: Header comments are clear and compliant
The introductory comments follow RFC 9116 conventions and provide helpful context for researchers.
Encryption: https://keys.openpgp.org/vks/v1/by-fingerprint/5461B0B9C1CCFB6E53A6760FC5D4DCC26C348C7B | ||
Preferred-Languages: en | ||
Canonical: https://unraid.net/.well-known/security.txt | ||
Expires: 2030-12-31T23:59:00.000Z |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Shorten the expiration interval
An expiration date in 2030 is overly long. RFC 9116 recommends rotating this file periodically (e.g., every 6–12 months) to ensure the policy stays up to date.
Contact: mailto:security@unraid.net | ||
Policy: https://unraid.net/policies | ||
Encryption: https://keys.openpgp.org/vks/v1/by-fingerprint/5461B0B9C1CCFB6E53A6760FC5D4DCC26C348C7B | ||
Preferred-Languages: en | ||
Canonical: https://unraid.net/.well-known/security.txt | ||
Expires: 2030-12-31T23:59:00.000Z | ||
Signature: https://unraid.net/.well-known/security.txt.sig |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing signature file
Your Signature: https://unraid.net/.well-known/security.txt.sig
entry requires the accompanying security.txt.sig
file. Please include the PGP signature at that path or update the URL to point to an existing signature.
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Before Submitting This PR, Please Ensure You Have Completed The Following:
Summary by CodeRabbit