I scanned 5 popular OSS repos in 5 minutes. Here's what I found.
A new tool called scan.html allows users to analyze public GitHub repositories for CI workflow issues. The author tested this tool on five popular open-source repositories, revealing common problems across them. Key findings include missing timeouts, concurrency settings, and caching configurations that could lead to increased costs and potential CI failures.
- ▪The scan.html tool fetches .github/workflows/*.yml files and generates a report using ci-doctor and gha-budget.
- ▪All five repositories tested are maintained by experienced engineers and are significant in the npm ecosystem.
- ▪Common issues identified include missing timeouts, concurrency settings, and caching configurations, which can lead to increased CI costs.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3901311) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } depmedicdev-byte Posted on Apr 28 • Originally published at depmedicdev-byte.github.io I scanned 5 popular OSS repos in 5 minutes. Here's what I found. #opensource #devops #ci #github Earlier today I shipped scan.html: a one-page in-browser tool that takes any public GitHub repo URL, fetches its .github/workflows/*.yml, and returns a per-workflow report using ci-doctor (14 rules) and gha-budget (per-job pricing). Runs entirely client-side via the GitHub public API.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV Community.
Discussion
0 commentsMore from DEV Community
