gaganhr94 opened a new pull request, #60551: URL: https://github.com/apache/doris/pull/60551
### What problem does this PR solve? Issue Number: close #60508 Related PR: #xxx Problem Summary: The repository currently does not publish OpenSSF Scorecard results to the public Scorecard API (https://api.securityscorecards.dev/). As a result, users and downstream projects cannot easily discover or track the project’s security best-practice posture in a standardized, automated way. The absence of published results reduces visibility and makes it harder for consumers to assess the project using common tooling. ### Release note None ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [ ] Regression test - [ ] Unit Test - [ ] Manual test (add detailed scripts or steps below) - [X] No need to test or manual test. Explain why: - [ ] This is a refactor/code format and no logic has been changed. - [ ] Previous test can cover this change. - [X] No code files have been changed. - [ ] Other reason <!-- Add your reason? --> - Behavior changed: - [X] No. - [ ] Yes. <!-- Explain the behavior change --> - Does this need documentation? - [X] No. - [ ] Yes. <!-- Add document PR link here. eg: https://github.com/apache/doris-website/pull/1214 --> ### Check List (For Reviewer who merge this PR) - [ ] Confirm the release note - [ ] Confirm test cases - [ ] Confirm document - [ ] Add branch pick label <!-- Add branch pick label that this PR should merge into --> --- ### What problem was fixed The repository currently does not publish OpenSSF Scorecard results to the public Scorecard API (https://api.securityscorecards.dev/). As a result, users and downstream projects cannot easily discover or track the project’s security best-practice posture in a standardized, automated way. ### How it was fixed This was addressed by adding an OpenSSF Scorecard GitHub Actions workflow that runs on scheduled intervals and on relevant branch updates. The workflow executes the Scorecard analysis, generates a SARIF report, and uploads the results to GitHub Code Scanning for visibility. ### Which behaviors were modified Previous behavior: No automated push of OpenSSF scorecard to the scorecard API. Current behavior: Scorecard analysis runs automatically on a schedule and on selected branches. ### Why this was modified: The absence of published results reduces visibility and makes it harder for consumers to assess the project using common tooling. So the scorecard workflow was added so that the project can be scored on various security criterias, and helps the user confidently use the project. ### Potential impact: No impact on runtime behavior or production code. Improves overall project security posture and audit readiness. ### What features were added Automated OpenSSF Scorecard scanning via GitHub Actions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
