Unmaintained open source and Irish firms
Whether an open source part under your system stays maintained is its maintainer's decision, but what a change would cost you is settled in your own offer and contract.
- Published
- Updated
- Reading time
- 7 min read
- Editor
- David Lahuta
In short
- On 12 February 2026 MinIO, an open source storage server, marked its open repository as no longer maintained and pointed users to its own AIStor editions.1
- In 2024 Redis moved new versions from an open source licence to licences that limit offering it as a competing service, and in 2025 it added an open source licence again.68
- A buyer cannot stop such a turn. He can ask three questions before he buys, who maintains each part, under which licence, and what a change would cost.
- The answers belong in the offer and the contract, together with who pays if a part has to be replaced.
What happened to the free edition in February 2026?
MinIO is a server for storing files and other large amounts of data, published on GitHub under the GNU AGPL v3 open source licence.2 More than 60,000 people had marked its repository with a star when we read it in November 2026.2 The project was not dropped in one day. Its own repository shows the steps.
| Date | What the project's own pages said |
|---|---|
| 15 October 2025 | The free community edition is distributed as source code only, with no more ready-built releases. The last release carries this date.2 |
| 3 December 2025 | The repository is "in a maintenance-only state". No new features, and critical security fixes "may be evaluated on a case-by-case basis".3 |
| 23 December 2025 | New subscription tiers of the commercial product AIStor, among them a free licence for a single server and paid editions for several servers.4 |
| 12 February 2026 | The notice at the top reads "THIS REPOSITORY IS NO LONGER MAINTAINED" and lists AIStor Free and AIStor Enterprise as the alternatives.1 |
When we read it on 17 November 2026, the repository was archived on GitHub.2 An archived repository is read only for all users, so nobody can add a fix to it there.5 The code itself has not gone away. It stays available under the AGPL, and anyone may still use, change and share it on the licence's terms.2 The project's own text also says that the licence gives no party any obligation to support, maintain or warrant the software.2
For a company whose system stores its documents in this server, the practical question is simple. Who will fix the next security flaw, and at what price?
How did another product change its licence and come back?
On 20 March 2024 Redis, a database that keeps its data in working memory for speed and by its own account serves millions of developers, announced that from version 7.4 it would no longer be released under the open source BSD licence.67 New versions came under two source-available licences, which let anyone read the code but limit some uses.6 Redis said plainly that neither licence is approved by the Open Source Initiative.6 The main limit concerned cloud providers and others offering Redis as a competing service, while hosting it for a company's own internal use stayed permitted.6 Redis gave its reason as well. Most of its commercial sales went through the largest cloud providers, which in its words commoditise its investments.6
Two things in the same announcement matter to a buyer. Versions released before the change keep their old licence and may be used indefinitely.6 Redis also said it would keep fixing critical security flaws in those older versions only until a later release, Community Edition 9.0.6
Eight days later, on 28 March 2024, the Linux Foundation announced Valkey, an open source alternative that continues from Redis 7.2.4 under the BSD licence, with support from Amazon Web Services, Google Cloud, Oracle, Ericsson and Snap.7 On 1 May 2025 Redis added the GNU AGPL v3, an approved open source licence, as an option from Redis 8.8 In the same post Redis wrote that the earlier change had hurt the company's relationship with the community, and that AWS and Google now maintain their own fork.8
The lesson is not about one company. The licence of the next version can change, the versions you already have keep theirs, and a fork maintained by others may or may not appear.
What does an open source licence promise, and what not?
An open source licence is a set of rights. The Open Source Definition requires, among other things, that the licence lets anyone give the software away or sell it, change it and use it in any field.9 It does not require anybody to keep the software up to date. MinIO's own text says this in so many words.2
Two further distinctions are worth knowing before a purchase.
- Source-available is not open source. You may read the code, but the licence limits what you may do with it, as with the Redis licences of 2024.6
- Some open licences come with duties. Under the GNU AGPL, whoever changes the software and lets users work with it over a network must offer those users the changed source code.10 If your supplier changes such a part and runs it for you, you should know who fulfils that duty.
Which questions show whether a part will stay maintained?
Three groups of questions cover most of it, who maintains the part, under which licence, and what a change would cost. Your supplier should be able to answer them for every part your system cannot run without.
| Question | Why it matters | A good answer |
|---|---|---|
| Who maintains the part, one company, a foundation or several companies? | One company can change course on its own, as the two cases show.16 | Names the maintainer and how the project is governed |
| Is it still maintained today? | A project with no recent work may not be patched. One public measure scores best a project with at least one change a week over the last 90 days, and worst an archived one.11 | Shows recent releases and security fixes |
| Do several organisations contribute? | The same measure looks for recent contributors from at least three companies.11 | Names who besides the main company works on it |
| Under which licence is the version we get? | Open source, source-available and commercial licences allow different uses.69 | Names the licence of each part and what it allows us |
| Does the licence bring duties for us or for you? | The AGPL asks for changed source code to be offered to network users.10 | Says who fulfils the duty and how |
| What happens if the part stops being maintained or changes its licence? | The free edition may end while your system still needs it.1 | Names the alternative, a fork, a paid edition or a replacement, and its rough cost |
| Who pays for the switch? | A forced replacement is unplanned work. | Settled in the contract |
The same public measure adds a fair warning. A small, finished piece of software may need no changes at all, so a quiet project is a reason to look closer, not a verdict.11
What should the offer and the contract say?
Most of these answers cost a supplier little to write down before the contract is signed, and a great deal to argue about afterwards.
Before you decide
- A list of the main parts the system rests on, with the version, the licence and the maintainer of each.
- For every part the system cannot run without, how the supplier judges that it is maintained, and the alternative if it stops.
- The supplier keeps the parts updated and patched for the agreed support period, including a part whose free edition ends.
- The supplier tells you in writing when a key part changes its licence or stops being maintained, and proposes what to do.
- Who bears the cost of replacing a part, and up to what amount, is stated in advance.
- Duties that come with a licence, such as offering changed source code, are fulfilled by the supplier.
- Any paid edition the system needs is named in the offer with its price, so it does not appear later as a surprise.
- You receive the source code and what is needed to build it, so another supplier can continue if needed.
None of this asks a supplier to promise what a third party will do. It asks him to know what he builds on and to carry the consequences he can foresee.
What this means for a company in Europe
The EU's Cyber Resilience Act, Regulation (EU) 2024/2847, turns part of this list into a duty for manufacturers of products with digital elements, mainly from 11 December 2027.12 They must exercise due diligence when they integrate components from third parties, including free and open source components.12 A vulnerability found in such a component must be reported to whoever maintains it.12 They must also document the components of their product in a software bill of materials, a machine-readable list covering at least the top-level dependencies.12 The regulation also gives a role to open source software stewards, organisations that support the development of an open source product over the long term and must keep a documented cybersecurity policy for it.12 A buyer can ask for the same list and the same care today.
Next step
If you are planning a purchase, we are glad to go through the parts it rests on with you in a short meeting. What you do with the result is entirely your decision.
Sources
- 1. MinIO, minio/minio repository on GitHub, commit 7aac2a2 "update README.md format and clarify state of the project" (12 February 2026). Read on 17 November 2026
- 2. MinIO, minio/minio repository on GitHub, README and releases (archived repository). Read on 17 November 2026
- 3. MinIO, minio/minio repository on GitHub, commit 27742d4 "update README.md maintenance mode" (3 December 2025). Read on 17 November 2026
- 4. MinIO, Introducing new subscription tiers for MinIO AIStor, Free, Enterprise Lite and Enterprise (23 December 2025). Read on 17 November 2026
- 5. GitHub Docs, Archiving repositories. Read on 17 November 2026
- 6. Redis, Redis adopts dual source-available licensing, with FAQ (20 March 2024). Read on 17 November 2026
- 7. The Linux Foundation, Linux Foundation launches open source Valkey community (28 March 2024). Read on 17 November 2026
- 8. Redis, Redis is now available under the AGPLv3 open source license (1 May 2025). Read on 17 November 2026
- 9. Open Source Initiative, The Open Source Definition. Read on 17 November 2026
- 10. Free Software Foundation, GNU Affero General Public License, version 3, section 13. Read on 17 November 2026
- 11. OpenSSF Scorecard, checks documentation (Maintained, Contributors). Read on 17 November 2026
- 12. Regulation (EU) 2024/2847 (Cyber Resilience Act), Articles 3(14), 13(5), 13(6), 24 and 71, Annex I Part II, Official Journal of the EU. Read on 17 November 2026
Change log
- Published.