Snyk
snyk.io
Repository configuration · changed within 730 days · Source checked 2026-10-12
CircleCI configuration for the Snyk CLI repository only; file last changed 2026-10-09. Builds and paid use unverified.
← All company lists
Developer infrastructure · October 2026 research
Companies and websites using CircleCI
Find companies and properties to review for CircleCI services and integrations.
The research date describes the saved research. Inclusion does not confirm present use or a paid subscription.
CircleCI research summary
21 reviewed company accounts
Research dated
21 reviewed company accounts: 18 publish CircleCI configuration in a company-owned public repository and 3 describe their own CircleCI workflows in a company engineering article. Each repository record covers that repository only. Current builds, payment and company-wide use are unverified.
Download the contact-free examples (CSV)What this research covers
This page publishes the source mix, findings and four contact-free examples from the 21-account CircleCI cohort. The full account file is not offered.
Reviewed contact-free examples
These approved examples illustrate the 2026-10-12 research. They are not a representative sample of all customers.
RevenueCat
revenuecat.com
Repository configuration · changed within 730 days · Source checked 2026-10-12
CircleCI configuration for the RevenueCat Flutter SDK repository only; file last changed 2026-10-08. Builds and paid use unverified.
InfluxData
influxdata.com
Repository configuration · changed within 730 days · Source checked 2026-10-12
CircleCI configuration for the Telegraf repository only; file last changed 2026-10-08. Builds and paid use unverified.
OpenGamma
opengamma.com
Repository configuration · changed within 730 days · Source checked 2026-10-12
CircleCI configuration for the Strata library repository only; file last changed 2026-10-07. Builds and paid use unverified.
What we found in this list
WhosBuilt analysis of the saved October 2026 research. Findings describe this selected cohort, not market share.
14 / 18 changed within 730 days
14 of 18 configuration files changed in the last two years
14 of the 18 repository records have a CircleCI file last changed within 730 days of the 2026-10-12 check, and 9 changed between 2026-09-22 and 2026-10-09. The other 4 were last changed between 2019 and 2023.
A file change shows maintained configuration, not an enabled pipeline or a paid plan.
Research 2026-10-12 · repository configuration records · WhosBuilt saved-record analysis
7 / 18 repository records
Seven repositories are SDKs, libraries, plugins or integrations
7 of the 18 repository records describe their project as an SDK, library, plugin, binding or integration. These files cover packages the companies maintain for others.
Package CI does not show which CI provider the same company uses for its private applications.
Research 2026-10-12 · repository configuration records · WhosBuilt saved-record analysis
2 / 18 repository records
Two root configs hand off to generated pipelines
2 of the 18 root configuration files are CircleCI setup configurations that continue into a generated or selected pipeline. One of the three company articles describes the same pattern for a monorepo with path filtering.
The jobs that run after the handoff are not in the checked root file and were not inspected.
Research 2026-10-12 · repository configuration records · WhosBuilt saved-record analysis
How this list was checked
Sources checked on 2026-10-12, 02:45–03:02 UTC. Configuration files were last changed between 2019-03-29 and 2026-10-09. Two company articles are dated 2018-12-07 and 2025-07-25; a third has no established publication date. Check times record retrieval, not current use.
21 reviewed company accounts: 18 publish CircleCI configuration in a company-owned public repository and 3 describe their own CircleCI workflows in a company engineering article. Each repository record covers that repository only. Current builds, payment and company-wide use are unverified.
| Source class | Count | Scope |
|---|---|---|
| Repository configuration · changed within 730 days | 14 | A .circleci/config.yml file at a checked public default-branch revision, last changed within 730 days of the check. A file change does not confirm enabled pipelines. |
| Repository configuration · older file history | 4 | The same configuration check, with the file last changed between 2019 and 2023. Treat these records as dated history. |
| Company engineering article · dated | 2 | The company describes its own CircleCI workflows at the publication date. |
| Company engineering article · undated | 1 | A company-authored description of its own CircleCI workflow without an established publication date. |
14 of 18 configuration files changed in the last two years: Denominator: the 18 accepted repository configuration records. Use the last commit that changed .circleci/config.yml at the checked revision, not the retrieval date. WhosBuilt analysis of accepted fields in the dated October 12 cohort; no source refresh.
Seven repositories are SDKs, libraries, plugins or integrations: Denominator: the 18 accepted repository configuration records; the purpose keywords are not a full repository taxonomy. Reviewed the source purpose description of each accepted repository. WhosBuilt analysis of accepted fields in the dated October 12 cohort; no source refresh.
Two root configs hand off to generated pipelines: Denominator: the 18 accepted repository configuration records. Reviewed each root file's setup and continuation declarations against CircleCI's documentation. WhosBuilt analysis of accepted fields in the dated October 12 cohort; no source refresh.
- One configuration file or company article supports each account. Other repositories, private applications and later changes were not checked.
- Public files and articles do not confirm current builds, a paid plan, company-wide use or buying intent. Public repositories are often SDKs, libraries and open-source projects; they do not show which CI the company uses for private applications.
- The cohort came from public repository searches and company engineering articles. Counts describe this list, not CircleCI's customer base.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.