C001 — OSS CI Adoption Rate Around 40% — Input¶
Contents¶
Original Text¶
Only approximately 40% of open source projects use continuous integration at all.
Clarified for Testability¶
Approximately 40% of open source projects hosted on major platforms (e.g., GitHub) have adopted continuous integration (CI) — that is, automated build/test pipelines triggered on commits or pull requests — as of recent empirical studies (2020-2025).
Embedded Assumptions Surfaced¶
- Assumes a measurable, agreed-upon definition of 'using continuous integration' (e.g., presence of CI configuration files, CI service badges, or evidence of CI runs).
- Assumes the 40% figure applies broadly across all open source projects rather than a specific subset (e.g., only actively maintained projects, or only projects above a certain size).
- Assumes 'open source projects' refers primarily to GitHub-hosted repositories, which is where most empirical studies sample from.
Scope¶
| Dimension | Value |
|---|---|
| Domain | Software engineering — CI/CD adoption in open source ecosystems |
| Timeframe | 2020-2025 (recent empirical studies) |
| Testability | Testable via empirical studies measuring CI adoption rates across GitHub repositories, looking for CI configuration files (e.g., .github/workflows/, .travis.yml, circle.yml, Jenkinsfile) or CI service API data. |
Vocabulary Map¶
Primary Terms: continuous integration, CI adoption, open source projects, CI/CD
Domain Variants: build automation, automated testing pipeline, CI service usage, DevOps adoption, GitHub Actions adoption
Related Concepts: continuous delivery, continuous deployment, CI configuration, Travis CI, GitHub Actions, CircleCI, Jenkins, CI/CD maturity