Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add OpenSSF Scorecard where available #195

Merged
merged 1 commit into from
May 15, 2024
Merged

Add OpenSSF Scorecard where available #195

merged 1 commit into from
May 15, 2024

Conversation

ryjones
Copy link
Contributor

@ryjones ryjones commented May 14, 2024

These are the existing scorecards.

@ryjones ryjones requested review from dstebila and baentsch May 14, 2024 13:23
@dstebila dstebila merged commit a723830 into open-quantum-safe:main May 15, 2024
1 check passed
@baentsch
Copy link
Member

As this is now publicly available, I'd strongly suggest working on improving those scores that are published (create issues in those sub projects?).

@dstebila
Copy link
Member

Agreed. I believe it was an action item for @planetf1 to add issues for these in the respective repositories.

@planetf1
Copy link

I opened open-quantum-safe/tsc#27 for followup actions across other repos. Comments welcome there!

@baentsch
Copy link
Member

I opened open-quantum-safe/tsc#27 for followup actions across other repos. Comments welcome there!

I do not think this was the (t)ask: I think the idea was to have single issues open (and resolve them) in each of those sub projects where you already publish scores (liboqs, liboqs-go and liboqs-rust) to clear them out before creating more bad impressions about the "security score" of further OQS sub projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants