Apache Hop community
Apache Hop and the Putki team
Putki is built on Apache Hop, an open-source project of the Apache Software Foundation. This page shows how Apache Hop is used and built, and the Putki team's part in it: over the last 12 months the client was downloaded 43,736 times from Apache's servers, and the Putki team wrote 47% of the project's commits and added 53% of its new unit-test files.
Every figure on this page comes from public sources: Apache Hop's git history, its GitHub repository, the ASF's download statistics and website analytics, and Docker Hub's usage figures. It is recalculated every week.
What this means for you
- Apache Hop is in growing use: unique downloads of the client from Apache's servers were 43,736 over the last 12 months, up 43% on the 12 months before.
- Apache Hop is built in the open by a community, and the team behind Putki is the largest group in it: about half of the code changes in the last 12 months, and more than half of the new tests. Other contributors write the other half.
- The same people manage Apache Hop releases and sit on its project management committee, so when you work with Putki you work with the people who build the engine.
- Every number here can be recounted from Apache Hop's public history.
Downloads
Unique downloads of the Apache Hop client from Apache's own download servers, counted every month by the ASF's infrastructure team, Jul 2023 to Oct 2026. Docker images and Maven artifacts come on top and are not counted here.
unique client downloads in Oct 2026
unique client downloads in the last 12 months
against the 12 months before
unique downloads of 2.19.0 in its first 3 months
Unique client downloads per month, all versions
The dotted lines mark the month each release first appears. No figures exist for Oct 2024; the line is broken there.
Unique downloads per release, first 12 months
- Counted downloads in the release's first months, as counted
- Projected estimate the months a recent release has not had yet; the whisker is the range
- Replaced within weeks a release the next one followed within a month
- Missing month the window includes a month without figures, so the count is low
| Release | First month | First 3 months | First 6 months | First 12 months |
|---|---|---|---|---|
| 2.20.0 | 2026-11 | not yet | not yet | not yet |
| 2.19.0 | 2026-08 | 7,999 | ≈ 9,8537,999 in 3 mo, 8,694–11,470 | ≈ 10,1817,999 in 3 mo, 9,123–11,793 |
| 2.18.1 | 2026-06 | 5,170 | ≈ 5,6875,545 in 5 mo, 5,622–5,728 | ≈ 6,0545,545 in 5 mo, 5,898–6,336 |
| 2.18.0 * | 2026-06 | 2,164 | ≈ 2,4352,348 in 5 mo, at 87 a month | ≈ 2,9572,348 in 5 mo, at 87 a month |
| 2.17.0 | 2026-02 | 7,048 | 10,106 | ≈ 10,97410,724 in 9 mo, 10,778–11,344 |
| 2.16.0 | 2025-11 | 5,984 | 7,371 | 8,019 |
| 2.15.0 | 2025-08 | 5,880 | 7,776 | 8,669 |
| 2.14.0 | 2025-05 | 4,949 | 6,735 | 7,156 |
| 2.13.0 * | 2025-04 | 2,128 | 2,429 | 2,638 |
| 2.12.0 | 2025-02 | 4,673 | 5,211 | 5,399 |
| 2.11.0 | 2024-12 | 4,385 | 4,767 | 5,001 |
| 2.10.0 * | 2024-11 | 2,437 | 2,672 | 2,776 |
| 2.9.0 | 2024-05 | 3,013 | 5,737 † | 6,467 † |
| 2.8.0 | 2024-03 | 3,753 | 4,079 | 4,326 † |
| 2.7.0 | 2023-12 | 3,027 | 3,860 | 4,111 † |
| 2.6.0 | 2023-09 | 1,995 | 2,247 | 2,405 |
≈ marks an estimate. * replaced by the next release within a month. † the window includes a month without figures.
Docker images
Pulls of the Apache Hop images on Docker Hub (apache/hop, apache/hop-web, apache/hop-dataflow-template), from Docker Hub's monthly usage figures, Jan 2025 to Oct 2026. Docker counts unique IP addresses per image tag; the figures here add those up.
unique IPs pulled a Hop image in Oct 2026
unique IPs over the last 12 months, month by month
pulls over the last 12 months
Unique IPs pulling a Hop image, per month
| Image, last 12 months | Unique IPs | Pulls | Pulls per IP |
|---|---|---|---|
| apache/hop | 56,483 | 173,207 | 3.1 |
| apache/hop-web | 65,569 | 272,680 | 4.2 |
| apache/hop-dataflow-template | 28,332 | 48,084 | 1.7 |
Pulls lead to the wrong reading on their own: one machine pulling in a loop adds tens of thousands in a month. Version checks, a pull that finds the image already current, are not counted.
Website visits
Visits to hop.apache.org, the project's website with its documentation, download page and blog, counted by the ASF's own analytics, Jun 2022 to Oct 2026.
visits to hop.apache.org in Oct 2026
visits a month on average, last 12 months
against the 12 months before
pages viewed per visit
Visits per month
Left out: Dec 2024, Sep 2026. Tracking was down for 3 days or more in that month, so its count would read as a drop.
The last 12 months
2025-11-05 to 2026-11-05.
of all commits
of the commits that add or change tests
of the new unit-test files
of the new integration-test files
Issues and pull requests
From the apache/hop GitHub repository, with automated accounts left out. An issue counts as resolved when GitHub closes it as completed, which includes closing it with a merged pull request.
pull requests merged per week
issues resolved per week
of merged pull requests came from the Putki team
people opened pull requests in the last 12 months
Pull requests merged per quarter
- All contributors 691 in Q3 26
- Putki team 308 in Q3 26
Issues per quarter
- Opened 531 in Q3 26
- Resolved 902 in Q3 26
People active per quarter
- Opening pull requests 27 in Q3 26
- Opening issues 75 in Q3 26
People new to the project per quarter
- First pull request 10 in Q3 26
- First issue or pull request 37 in Q3 26
The last point is the quarter still running.
| Last 12 weeks | Total | Per week | Putki team |
|---|---|---|---|
| Issues opened | 604 | 50.3 | — |
| Issues resolved | 760 | 63.3 | — |
| Pull requests opened | 737 | 61.4 | — |
| Pull requests merged | 722 | 60.2 | 46%334 of 722 |
| Pull requests closed without merging | 13 | 1.1 | — |
How the work is spread
People grouped by how many issues or pull requests each of them opened in the last 12 months. Amber is the group's share of the people, pale its share of the work, and blue the Putki team's part of that work.
Issues opened per person
1,459 issues from 179 people, 109 of them new to the project.
Pull requests opened per person
1,684 pull requests from 59 people, 38 of them new to the project.
- Share of the people
- Share of the work
- Putki team 46% of pull requests, 28% of issues
| Opened each | Issue reporters | Issues | Pull request authors | Pull requests |
|---|---|---|---|---|
| 10+ | 1911% | 1,17180% | 1119% | 1,57894% |
| 4–9 | 179% | 936% | 712% | 392% |
| 3 | 116% | 332% | 814% | 241% |
| 2 | 3017% | 604% | 1017% | 201% |
| 1 | 10257% | 1027% | 2339% | 231% |
Who comes back, and who watches
Issue reporters of the last 6 months, and the people who starred, forked or watch the repository against everyone who took part.
of issue reporters in the last 6 months were returning
new reporters filed a single issue
people starred the repository
Share of commits per quarter
The Putki team's share of all commits, for the last 12 quarters. The dashed line marks half. The current quarter is still running.
Per release
Commits, bugs fixed and new tests between one release and the one before it, and the tests in the source of each release. The last point and the first row are the work on the main branch that has not been released yet.
Growth of the test suites
- Unit tests 2,665 in 2.10, 14,702 in 2.20, 15,088 on main
- Integration tests 263 in 2.10, 647 in 2.20, 667 on main
Each line is relative to its size in 2.10.
Bugs fixed
- All contributors 49 in 2.10, 271 in 2.20
- Putki team 23 in 2.10, 116 in 2.20
Released versions only: the release in progress and patch releases are in the table.
| Release | Tagged | Commits | Bugs fixed | New unit-test files | New integration-test files | Unit tests in the release | Integration tests in the release |
|---|---|---|---|---|---|---|---|
| Since 2.20.0, unreleased | 2026-11 | 59%51 of 87 | 56%22 of 39 | 50%36 of 72 | 32%38 of 119 | 15,088 | 667 |
| 2.20.0 | 2026-10 | 46%297 of 646 | 43%116 of 271 | 51%645 of 1,275 | 84%1,556 of 1,862 | 14,702 | 647 |
| 2.19.0 | 2026-08 | 47%178 of 381 | 47%78 of 166 | 51%226 of 439 | 40%245 of 606 | 7,637 | 471 |
| 2.18.1 | 2026-06 | 90%18 of 20 | 12 of 15 | 0 of 4 | 100%47 of 47 | 5,234 | 382 |
| 2.18.0 | 2026-05 | 47%151 of 322 | 56%70 of 126 | 66%140 of 211 | 36%202 of 562 | 5,169 | 375 |
| 2.17.0 | 2026-02 | 49%100 of 204 | 40%38 of 94 | 75%18 of 24 | 60%85 of 142 | 3,919 | 319 |
| 2.16.0 | 2025-11 | 48%74 of 155 | 45%25 of 55 | 77%59 of 77 | 41%39 of 95 | 3,655 | 304 |
| 2.15.0 | 2025-08 | 29%38 of 132 | 17%9 of 54 | 3 of 3 | 21%9 of 43 | 2,788 | 288 |
| 2.14.0 | 2025-05 | 57%37 of 65 | 11 of 16 | 0 of 1 | 100%53 of 53 | 2,739 | 284 |
| 2.13.0 | 2025-04 | 74%84 of 114 | 62%21 of 34 | 4 of 6 | 100%33 of 33 | 2,738 | 278 |
| 2.12.0 | 2025-02 | 48%45 of 94 | 31%8 of 26 | — | 8%3 of 37 | 2,695 | 273 |
| 2.11.0 | 2024-12 | 71%139 of 195 | 59%23 of 39 | 1 of 7 | 79%19 of 24 | 2,681 | 269 |
| 2.10.0 | 2024-10 | 60%139 of 233 | 47%23 of 49 | 0 of 3 | 33%10 of 30 | 2,665 | 263 |
Below 20, only the count is shown: a percentage of a handful is noise.
Over time
The Putki team's share over rolling windows ending today. All time starts with the first Apache Hop commit in 2019.
| Team share of | 6 months | 12 months | 24 months | All time |
|---|---|---|---|---|
| Commits | 47%550 of 1,158 | 47%779 of 1,643 | 49%1,102 of 2,271 | 40%2,810 of 6,978 |
| Commits that add or change tests | 47%377 of 796 | 46%440 of 956 | 48%524 of 1,095 | 42%910 of 2,155 |
| New unit-test files | 51%949 of 1,844 | 53%1,065 of 2,021 | 54%1,131 of 2,110 | 38%1,408 of 3,754 |
| New integration-test files | 72%1,923 of 2,677 | 65%2,126 of 3,294 | 64%2,270 of 3,564 | 53%2,817 of 5,324 |
| Lines added and removed | 60%927,484 of 1,546,150 | 57%1,094,406 of 1,931,379 | 58%1,260,073 of 2,187,621 | 35%3,358,588 of 9,568,555 |
How we count
- Source. The main branch of the Apache Hop repository and its release tags. Anyone can repeat these counts from a clone of github.com/apache/hop.
- Commits. Counted like GitHub's contributors graph: merge commits are left out, and each commit counts once for its author, matched by email address. Apache Hop squash-merges pull requests, so a pull request counts as one commit for the person who wrote it.
- Automation. Translation syncs and automated dependency updates are left out of every total: 86 commits in the last 12 months. GitHub's graph includes them, and it only counts addresses linked to a GitHub account, so its totals differ slightly.
- The Putki team is the Putki engineers who contribute to Apache Hop, counted together, including their commits from before Putki existed.
- New test files are files a commit adds: Java files under
src/test, and anything underintegration-tests(pipelines, workflows, test definitions, database setups). Moved or renamed files are not new. One new integration-test project adds many files at once, so that measure moves in steps. - Tests in a release are counted in the source tree of the release tag: unit tests are
@Testmethods, and integration tests are the test workflows Apache Hop's integration-test runner executes, one permainworkflow. Apache tags a release as the candidate that passed the vote. - Bugs fixed are the GitHub issues of type Bug in the release's milestone (or labelled bug, for issues from before GitHub had issue types), closed as completed. A bug counts for the Putki team when the pull request or commit that closed it is the team's. When a bug was closed by hand, it counts for the team only if every commit in that release that mentions it is the team's. Any bug we cannot attribute counts for other contributors, so the team figure is never overstated: 76 of 984 bugs on this page.
- Lines are lines added plus lines removed, as on GitHub. Large moves and generated files dominate this measure, so read it next to the commit counts.
- Downloads are the ASF's own monthly counts for Apache Hop on dlcdn.apache.org and downloads.apache.org, for the client zip of each version. A unique download is one address in one month, so a person who downloads in two months counts twice. Downloads from archive.apache.org, Docker Hub and Maven Central are not in these figures.
- Downloads per release start in the first month a release is downloaded. Releases from before the ASF figures began, in Jul 2023, are left out.
- Projected downloads fill in the months a recent release has not had yet: its downloads so far, multiplied by how much earlier releases grew over the same months (the median; the range is the lowest and highest growth seen). A release the next one replaced within a month is projected at its last month's rate instead. Projections are estimates and are always marked.
- Issues and pull requests come from the apache/hop GitHub repository. Automated accounts (dependency updates, translation syncs) are left out: 347 issues and pull requests in all. Pull requests are counted for the person who opened them; co-authors and reviewers are not counted.
- Docker images are Docker Hub's monthly usage figures for the Apache Hop images. A unique IP is counted per image tag, so an address that pulls two tags counts twice; pulls are pulls by tag plus pulls by digest; version checks are left out. Docker Hub publishes these to the namespace owner only, so they are added to this page by hand each month.
- Website visits are the ASF's own analytics for the project website (analytics.apache.org, site 11). A month in which tracking was down for 3 days or more is left out rather than shown as a drop.
- Taking part means opening an issue or pull request, commenting on one, or posting in GitHub Discussions. Comments are read for the last 12 months only, so someone whose only activity is an older comment counts as never having taken part.
- Not counted: reviews, merging other people's pull requests, issue triage, answering questions, and managing releases.
Why Putki runs this, not Apache Hop
Why it is Putki work
If you depend on Apache Hop, you should be able to see who builds it. Putki customers pay for this team's time, so its share of the work is also what they are buying.
What goes to Apache Hop
Everything counted here is done in Apache Hop, for everyone. Putki adds what an open-source project cannot do itself, such as tests on paid accounts and support under contract.
Who runs this, and how to work with them
The Putki team are Apache Hop committers and members of its project management committee. Putki customers get the same people under contract, with support for the version they run.