BUG A link within checks.md for Security-Policy results in a 404

[shissam]

Describe the bug
A clear and concise description of what the bug is.

https://github.com/ossf/scorecard/blob/main/docs/checks.md#security-policy for Security-Policy has a link to "coordinated vulnerability disclosure guidelines" which points to https://github.com/ossf/oss-vulnerability-guide/blob/main/guide.md however in issue #2137, a link to https://github.com/google/oss-vulnerability-guide/blob/main/guide.md appears to be the link that should be used "guidelines"

Reproduction steps
Steps to reproduce the behavior:

1. Launch to ossf/scorecard
2. Navigate down to "Checks" or page search for "Security-Policy" (currently the 5th match) and click through Security-Policy
3. Once there, under Remediations steps, click through on coordinated vulnerability disclosure guidelines
4. Observe the 404

Expected behavior
Expect to not get a 404 and be given the promised guide.md to support Security-Policy remediation.

Additional context
It appears that https://github.com/google/oss-vulnerability-guide/blob/main/guide.md is the correct link - not sure. this would be a change from /ossf/ to /google/

[shissam]

I can fix this in PR #2195 just need confirmation the google repo is where the link is intended to point for guide.md

[spencerschrock]

The OSSF one should be correct, the file just got renamed. Providing a permalink would prevent file renamings from leading to 404s, but then we lose out on content updates.

https://github.com/ossf/oss-vulnerability-guide/blob/main/maintainer-guide.md

[shissam]

if you concur - I'll squash this one now in PR #2195 if you think we're close enough.

[spencerschrock]

Sure. You've touched the check docs (and the yaml) anyway in the PR. Seems like a great time to update the link. Make sure to merge the latest changes from main, and should be ready to get the whole PR in.

[shissam]

done and PR pushed for integration test. I'll close this out now (can reopen if I botched it :-))