docs: add security policy - #3
Open
craigthackerx wants to merge 1 commit into
Open
Conversation
The repo had no SECURITY.md. Private vulnerability reporting is already enabled, so this documents that channel rather than introducing an email address that would need monitoring. Scope is written for what this project actually is: a static aggregator with no backend, where the interesting attack surface is untrusted upstream feed content reaching the browser or the build. Article content itself is explicitly out of scope and directed to the originating vendor, as is anything Dependabot already tracks. Supported versions reflects reality — the deployed site from master, with no backports. Tags here are historical markers, not releases.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
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
1 participant
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.
Adds
SECURITY.md. The repo had none, which is a conspicuous gap for a public repo that aggregates security advisories.Reporting channel
Points at GitHub private vulnerability reporting, which is already enabled on this repo, rather than an email address. That avoids publishing a personal address and avoids the failure mode where a policy names a mailbox nobody watches.
Scope
Written for what this project actually is — a static site, no backend, no accounts — so the realistic attack surface is untrusted upstream feed content reaching a viewer's browser or influencing the build:
data/feed.xmlExplicitly out of scope, so triage time isn't spent on them:
Supported versions
States the truth: only the deployed site from
master, no backports. The tags here (0.0.1,0.0.2) are historical markers, not supported releases.Documentation only — no code, workflow or dependency changes.