(Ͼ˳Ͽ)...Check-my-repo!!!
summary
An automated checker built on Repolinter with Node.js and Vue.js uses GitHub Actions to run nightly or on push and publishes results to GitHub Pages. It enforces 11 default rules (binaries, license, README, contributing, changelog, ownership, tests, code of conduct, security, support, badges) and replaces manual Excel audits, surfacing failing repos with prioritized badges. Deployed at Sauce Labs for OSPOs, it runs and redeploys automatically and is configurable via a simple JSON.
AI-written summary · about
chapters (11)
- 0:00Why we need rules
- 3:12Breaking bad rules
- 6:27Communication in open source
- 11:25Information imbalance
- 14:37Maintainers' challenges
- 16:21Introducing Check-my-repo
- 18:47Automation benefits
- 19:08High-priority rules
- 22:21Low-priority rules
- 24:07Live demo setup
- 25:12Conclusion and Q&A
related talks
08mAutomated Checks Before Publishing Open Source, a Few Years La...
16mFortify Your Code: Secure Your Supply Chain with Scorecard
39mManaging an Open Source Project
25mHow do you trust your open source software?
31mScorecard at Scale: Old and New Possibilities for Lifting Security on All Repositories
39mImplementing the OpenSSF Best Practices Badges & Scorecards Into Your Project
33mORT Automate compliance using Open Source & InnerSource
40mA Guide to Securing GitHub Based on Lessons Learned