Repository navigation
fix: add project section to Security Insights and expand README - #104
Merged
Merged
Conversation
## What/Why The OSPS Baseline scan flags OSPS-QA-04.01 and OSPS-DO-01.01 because security-insights.yml has no project section, so project.repositories and project.documentation.detailed-guide are empty. Add the project section and expand the README into the guide that detailed-guide points at. ## Proof it works cue vet passes against the Security Insights v2.2.0 schema. The scanner checks a non-empty project.repositories and a non-nil project.documentation.detailed-guide; both are now set. ## Risk Low. Metadata and README only. ## AI role Claude Opus 5.5 traced both checks in the scanner source and wrote the changes; I approved the approach. ## Review focus README accuracy. Signed-off-by: jmeridth <jmeridth@gmail.com>
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.
What/Why
The OSPS Baseline scan flags OSPS-QA-04.01 (subproject list) and OSPS-DO-01.01 (user guide) because
security-insights.ymlhas noproject:section. Both checks read from it. This adds the section, listing this repo and pointingdetailed-guideat the README. The README now covers setup, checks, content locations and deployment, so it works as that guide.Proof it works
cue vetpasses against the Security Insights v2.2.0 schema. The two code scanning alerts should close on the next OSPS scan after merge.AI role
Claude Opus 5.5 traced both checks in the scanner source and wrote the changes; I approved the approach.