-
Notifications
You must be signed in to change notification settings - Fork 497
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
Donate openssf-scorecard-monitor ecosystem #3204
Comments
@UlisesGascon -- my apologies for letting this linger! I'm going to run down the donation next steps starting early next week. |
Thanks @justaugustus! Looking forward for it! 🙌 |
Stale issue message |
ping @justaugustus 🙂 |
@UlisesGascon -- I've opened a request with our WG to discuss the donation: ossf/wg-best-practices-os-developers#238 Sorry again for the wait! |
Thanks a lot @justaugustus! :) |
This issue is stale because it has been open for 60 days with no activity. |
Reflecting the license scan results from ossf/wg-best-practices-os-developers#238 (comment) here as well:
|
This is complete with ossf/scorecard-monitor#79. |
@justaugustus suggested that we donate the project, and we started the process some time ago 🙂
The openssf-scorecard-monitor is a GitHub action that allows you to track the OpenSSF Scorecard in your organization and dependencies with automated markdown and JSON reports, plus optional GitHub issue alerts and many other cool features.
This tool is currently used by several organizations. For example, in the Node.js Security Working Group, we use it to monitor key projects in our regular meetings. Here is the report that we use.
@KoolTheba, who is also a co-maintainer, is very happy with the idea and interested in donating the comparator and visualizer tool that we use in the reports called openssf-scorecard-api-visualizer.
I had the opportunity to work closely with some of you in the last months, and I am super excited to team up 🙌.
I wanted to create this issue to add more visibility to the donation and open the discussion to other maintainers interested in helping us with the process.
What are our next steps? 🚀
The text was updated successfully, but these errors were encountered: