Repository navigation
Replace security placeholder issues with maintained guidance - #245
Merged
Merged
Conversation
This was referenced Sep 10, 2026
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.
Consolidate ten generic security reference issues (#190–199) into a maintained guide with project-specific completion evidence. Link the guide from the WG landing page and security issue form. Preserve original issues as historical sources, including their examples and access-coordination details.
Update guidance against current GitHub documentation: repository-scoped GITHUB_TOKEN where sufficient, current secret-scanning behavior, and current CVE-Bin-Tool location. Preserve the recorded Scorecard recommendation without introducing a new release gate. No project is declared compliant and no repository security settings change.
After merge, close the ten generic placeholders as superseded reference material, with a pointer to the guide. Actual project security tasks remain open. All ten were refreshed and have no comments or project assignments.
Validation: local file/section links, document structure, YAML parsing and whitespace checks pass. Required GitHub checks must pass before merge. PDFs unchanged.
The user authorized continued cleanup and push/merge after checks. Use the existing administrator review exception; this is not independent CODEOWNER approval.