docs(security): finish keeper→strongroom rename in SECURITY.md#52
Open
askalf wants to merge 1 commit into
Open
docs(security): finish keeper→strongroom rename in SECURITY.md#52askalf wants to merge 1 commit into
askalf wants to merge 1 commit into
Conversation
SECURITY.md still carried four keeper-era strings: the intro line, the private-advisory link (askalf/keeper/security/advisories/new - functioned only via the repo redirect), the report email subject, and the supported-versions line. This is the page a vulnerability reporter or CII reviewer reads; now consistent with the strongroom name. No process/SLA changes.
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.
SECURITY.md still said keeper in four places: the intro line, the private-advisory link (
askalf/keeper/security/advisories/new— worked only via repo redirect), the report email subject (keeper security), and the supported-versions line. All four now say strongroom. Docs-only, 4 lines; no process or SLA changes. This is the page a vulnerability reporter or bestpractices.dev reviewer reads — spotted while preparing the CII enrollment sheet.