Skip to content

Conversation

@jmeridth
Copy link
Contributor

@jmeridth jmeridth commented May 28, 2025

Pull Request

Proposed Changes

OSSF scorecard has proven to highlight security issues that don't necessarily match our proven practices and leaves unnecessary notices on our security tab. Removing.

Readiness Checklist

Author/Contributor

  • If documentation is needed for this change, has that been included in this pull request
  • run npm run lint and fix any linting issues that have been introduced
  • run npm run test and run tests
  • If publishing new data to the public (scorecards, security scan results, code quality results, live dashboards, etc.), please request review from @jeffrey-luszcz

Reviewer

  • Label as either bug, documentation, enhancement, infrastructure, maintenance, or breaking

OSSF scorecard has proven to highlight security issues that don't
necessarily match our proven practices and leaves unnecessary notices
on our security tab. Removing.

Signed-off-by: jmeridth <jmeridth@gmail.com>
@jmeridth jmeridth self-assigned this May 28, 2025
@jmeridth jmeridth requested review from a team as code owners May 28, 2025 22:27
@jmeridth jmeridth requested a review from zkoppert May 28, 2025 22:27
@wrslatz
Copy link
Contributor

wrslatz commented May 28, 2025

I believe GitHub's security hardening docs for Actions recommend using OSSF Scorecard (I recently contributed there, but I could be misremembering). Are there any open issues or discussions on which Scorecard findings aren't useful or accurate? Have there been any issues or improvements raised with OSSF Scorecard that we could track?

@jmeridth jmeridth closed this Jul 24, 2025
@jmeridth jmeridth deleted the jm_remove_ossf_scorecard branch July 24, 2025 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants