Notes5 min read

Your software has expiry dates. Check them before a buyer does.

Languages, frameworks and databases all publish the day their fixes stop, and most owners do not know theirs. A buyer's reviewer will. Our free stack check reads your project files in your browser and lays the dates out before anyone else does, each with a rating and the business impact, in a report you can keep.

Every piece of business software stands on parts with a published end date. The language it is written in, the framework, the database, the operating system under the containers: each has a vendor or a community that says, in advance, when fixes stop. PHP 8.2 stops getting security fixes on 31 December 2026. PostgreSQL 14 had its final release on 12 November 2026. On Amazon's managed databases, the extra charge for an old version starts on a fixed day, whether anyone in the company notices or not.

Owners rarely know these dates. A buyer's reviewer always looks them up. This note is about closing that gap cheaply, before it turns into a line in someone else's report.

Why owners miss them

Nothing breaks on the day. Software on an unsupported version runs the morning after exactly as it ran the night before. There is no outage, no invoice and no email from the vendor to the owner. What changes is quieter: new security flaws stay open, and the upgrade that will come one day grows with every release that is skipped.

The dates are scattered. Each language, framework, database and platform publishes its own schedule on its own page, in its own words: long-term support, standard support, extended support, security fixes only. Nobody in a small or mid-sized company is paid to read all of them.

And the knowledge sits with the team. Developers know which versions run; the owner knows customers, margins and the plan. A version number rarely reaches a board pack until someone outside asks for it, and in a sale that someone is the buyer.

What a buyer does with them

Early in a technical due diligence, the reviewer lists every component with its version and its support status. A component past its end of support becomes a finding with a severity. On its own it is usually modest. It becomes a deal point when the component holds customer data, when the upgrade is large and nobody has planned it, or when the cost of paid extended support is missing from the numbers. Then it moves into the terms: a price adjustment, a holdback, a condition to fix before closing or a specific disclosure. Our deal notes walk through real dates, for example PostgreSQL 14 and the cloud bill that grows by itself and .NET versions where one move is an upgrade and another a rewrite.

The gap between a finding the seller disclosed with a plan and one the buyer found alone is large. The first reads as a managed item. The second reads as a question about what else nobody looked at.

A two-minute check

We built a stack check for exactly this. Drop the files that describe your software: composer.json and composer.lock, package.json, requirements.txt or pyproject.toml, a Gemfile, a .csproj, pom.xml or build.gradle, a Dockerfile or docker-compose.yml, serverless or Terraform files. The page finds the languages, frameworks, databases and images in them and matches them against the dates in our calendar. Each date comes with a rating, the time left, what it means for an owner and for the business, a link to its official source and, where we have written one, a note on what it does to a deal.

It runs in your browser. The files are read on the page, and nothing is uploaded or stored. That was a design rule, not a feature: dependency files are rarely secret, but nobody preparing a sale should have to send them to a stranger to learn what the vendors already publish.

What is not in project files can be ticked by hand: Windows Server, Exchange, email that applications and devices send through Microsoft 365, and the rules that depend on where you sell, such as the European accessibility and cyber resilience rules.

How to read the result

The dates fall into three groups: already out of support or in force, in the next 12 months, and later. Every date also gets a rating on the same scale our reviews use, kept here to three levels:

  • High. Out of support now, or within six months. If a buyer finds it unplanned, it is likely to affect the price or the terms. Plan it now.
  • Medium. Ends within a year, support narrows or turns paid, or a rule starts to apply. It raises the cost of owning the product and belongs in this year's plan.
  • Low. Later dates and new releases. A line in the technology plan is enough.

The check never rates anything Critical. On our scale Critical means a finding that can stop a deal, and that depends on what the files do not show: whether the component holds customer data, whether it faces the internet, whether anyone in the company can still change it. A reviewer sets that, with the evidence in front of them.

Each line also says how long ago the date passed or how much time is left, and what it does to the business in plain words: no more fixes from the vendor, a recurring charge until the upgrade, or an obligation to check. What the check does not give is a price for the fix. The cost of an upgrade depends on the code, the tests and the integrations, not on the version number, and we do not put a number on what we cannot see.

One caution. A lock file or a container image names the version that actually runs. A file like composer.json or package.json names the oldest version the code allows, which can be older than what runs in production. Every match on the page shows the file and the line it came from, so untick whatever does not apply.

A report for the owner, the board or the data room

The result can be saved as a PDF. Add the name of the company or the product, and the report lists every date with its rating, the time left, the business impact and the official source. It says what was read from which file and what was ticked by hand, and it explains the ratings and the limits of the check. It is one document an owner can read in ten minutes and a board can take as one item on the agenda.

In a sale it does a second job. Put into the data room with a plan next to each High item, it turns what a buyer would have found into what the seller disclosed. The PDF is made by your own browser, like everything else on the page, so the files never leave it.

Keep the dates in front of you

The dates themselves can go into your own calendar as a file, or be copied as a plain list. The whole calendar can be added to Google Calendar, Apple Calendar or Outlook from our technology deadlines page, so new dates arrive by themselves, and the stack check sits one click away under the calendar there. Every date there is checked against its official source, such as the PHP supported versions page or Amazon's description of RDS Extended Support.

When a check is not enough

The stack check covers dated changes only. It does not scan code for vulnerabilities, read licenses, weigh architecture or ask who owns the accounts. If a buyer will read the company soon, a red-flag memo puts severity, cost and time to fix next to each item. If the sale is a year or more away, exit readiness closes the items month by month, so the list a buyer receives is short and already explained.

Questions

Does the stack check see my code?

No. It reads the files you drop on the page with your own browser and never sends them anywhere. Most of what it needs sits in dependency and build files, which name versions, not business logic. Nothing is stored after you close the page, and the page only counts that a check was run.

Which files give the most exact result?

Lock files and container definitions. composer.lock, package-lock.json, Gemfile.lock and the images in a Dockerfile or docker-compose.yml name the versions that actually run. composer.json or package.json name the oldest version the code allows, which can be older than production. Drop both kinds if you have them.

How does the check rate each date?

On the scale our reviews use, by the date and the kind of change. High: out of support now or within six months. Medium: ends within a year, support narrows or turns paid, or a rule applies. Low: later dates and new releases. It never rates anything Critical: that needs context the files do not show, such as customer data or exposure to the internet.

Can I share the result with a board or a buyer?

Yes. Save it as a PDF with the name of the company: every date with its rating, time left, business impact and source, what was read from which file, and the limits of the check. Your browser makes the PDF, so nothing is uploaded. In a sale, put it into the data room with a plan next to each High item.

Is an out-of-support component a deal breaker?

Rarely on its own. It becomes a deal point when it holds customer data, when the upgrade is large and unplanned, or when the cost of paid extended support is missing from the numbers. A component disclosed with a plan reads very differently from one a buyer finds alone.

What if something we run is not on the list?

The check covers the dates in our calendar: languages, frameworks, databases, platforms and rules with a dated change, each checked against its official source. The calendar grows every month. If a component that matters to you is missing, tell us and we will look at its schedule.

Written by
Yevhen Borovoi
FounderYevhen Borovoi

Founder of PERETZ, DeZZign, The Structure and NEX, partner at SCHOEFFEL. An engineer by training who reads a business as one system: strategy, product, technology, processes and economics.

Next step

Preparing a sale or looking at a target?

We reply within one business day. NDA before any documents change hands.