Which of these dates are in your stack?
Drop the files that describe your software, or tick what you run. The check matches them against our calendar of end-of-support dates and new rules, and shows what has already passed, what comes in the next twelve months and what each date means for an owner. It all happens in your browser: nothing you drop or paste is uploaded or stored.
- Dates checked
- 57
- Files read
- PHP, JS, Python, Ruby, .NET, Java, Docker
- Uploads
- None
- Report
- PDF, free
Your stack, against the calendar.
Or paste the text of a file
Read in your browser. Nothing is uploaded or stored.
Out of support now, or within six months. Likely to affect price or terms if a buyer finds it unplanned.
Ends within a year, support narrows or turns paid, or a rule applies. Belongs in this year's plan.
Later dates and new releases. A line in the technology plan.
Never set here: it needs context the files do not show, such as customer data or exposure to the internet. See how we rate findings.
A buyer will read the same list. A red-flag memo puts severity, cost and time to fix next to each item, and exit readiness closes them before a sale. For the accounts, domains and rights behind the code, take the ownership check.
Three steps, all on your side.
Read in your browser
The page reads the files you drop or the text you paste with your own browser. Nothing is sent to us or anyone else, and nothing is kept after you close the page.
Matched to the calendar
Versions are matched to the dates in our technology calendar: end of support, paid support and new rules, each checked against its official source.
Read for an owner
Every date comes with what it means for an owner, a link to the source and, where we have written one, a note on what it does to a deal.
The files it understands.
- PHP
- composer.json and composer.lock: PHP, Laravel, Symfony, Drupal, Magento and WordPress.
- JavaScript
- package.json, package-lock.json and .nvmrc: Node.js, Vue, Nuxt and Angular.
- Python and Ruby
- requirements.txt, pyproject.toml, Pipfile, .python-version, Gemfile and Gemfile.lock: Python, Django, Ruby and Rails.
- .NET and Java
- .csproj, global.json, web.config and packages.config: .NET and .NET Framework. pom.xml and build.gradle: Spring Boot and Android apps.
- Containers and cloud
- Dockerfile and docker-compose.yml: language, database and operating system images. serverless.yml, SAM templates and Terraform: AWS Lambda runtimes and Amazon RDS databases.
- The rest
- Windows Server, SQL Server on Windows, Exchange, Microsoft 365 email and the rules that depend on where you sell are not in project files. Tick them by hand.
Questions about the check.
Is my code uploaded anywhere?
No. The files are read by your own browser, on this page. Nothing you drop or paste is sent to us or to anyone else, and nothing is stored. The page only counts, without any content, that a check was run.
How exact is the result?
As exact as the files. A lock file or a container image names the version that runs. A file like composer.json names the oldest version the code allows, which may be older than what runs in production. Every match shows the file and the line it came from, so you can untick what does not apply.
What does it not cover?
Only what is in our calendar: languages, frameworks, databases, platforms and rules with a dated change. It does not scan code for vulnerabilities, read licenses or judge architecture. Those belong to a technical due diligence. Who owns the code, the accounts and the rights is the ownership check.
How is the severity set?
On the scale our reviews use, by the date and the kind of change only. 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. Critical is never set here: it needs context the files do not show, such as customer data or exposure to the internet, so a reviewer sets it. See how we rate findings.
Can I get a report?
Yes. Save the result as a PDF for the owner, the board or a data room: every date with its rating, time left, business impact and official source, and what was read from which file. The PDF is made by your own browser, so nothing leaves the page. You can also add the dates to your calendar as a file, copy them as a list, or subscribe to the whole calendar.
What should I do with the result?
Plan the items that come before a sale or a raise. If a buyer will read the stack soon, a red-flag memo puts severity, cost and time to fix next to each item, and exit readiness closes them month by month.
Deal notes on these dates.
· 6 minNov 19, 2026Your 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.Notes
· 5 minNov 19, 2026.NET 8, .NET 9 and .NET Framework 4.6.2: an upgrade and a rewrite in a dealSupport for .NET 8 and .NET 9 ended on 10 November 2026, and .NET Framework 4.6.2 follows on 12 January 2027. The names are close, the work behind them is not: one is usually a contained upgrade, the other can be a platform to rewrite. What a reviewer reads, how each turns into deal terms, and what a seller can still do.Notes
· 7 minNov 19, 2026PostgreSQL 14 in a deal: an unpatched database and a bill that grows by itselfPostgreSQL 14 received its final release on 12 November 2026, and on Amazon RDS and Aurora paid Extended Support starts on 1 March 2027. For a company sold or bought around that date, a database version becomes both a security finding and a new line in the cloud bill. What a buyer's reviewer reads, how it becomes a deal term, and what a seller can do now.Notes
· 7 minNov 19, 2026Certificates renewed by hand: the TLS change that reaches a dealSince March 2026 a public TLS certificate can be valid for at most 200 days, from March 2027 for at most 100 and from March 2029 for at most 47. Where renewal is automatic and watched, nothing changes. Around a sale it reaches certificates renewed by hand, installs and devices in the field, pinned mobile apps and the accounts that control the domains, and the outage tends to land after closing.Notes
· 7 minNov 19, 2026Windows Server 2016 and SQL Server in a deal: the fee is known, the move is notSQL Server 2016 left extended support in July 2026, Windows Server 2016 follows in January 2027 and SQL Server 2017 in October 2027. In smaller companies they often carry the accounting, the ERP and the internal systems. Microsoft sells security updates by the year, but the move to a supported version is the real project, and around a sale it is the part that gets priced.Notes
· 7 minNov 14, 2026Mail sent with a password: the Microsoft 365 change that reaches a dealAt the end of December 2026 Microsoft 365 turns off, by default, sending mail with a plain username and password. For most companies it is an IT ticket. Around a sale it reaches customer-facing mail, shared passwords and the tenant moves that follow closing. What a reviewer reads, when it becomes a deal point, and what a seller can close before a buyer sees it.Notes
· 6 minNov 14, 2026Symfony 6.4, Drupal 10 and PHP 8.2 in a deal that closes in 2027Three parts of a large share of PHP software lose support within five weeks at the end of 2026. For a company sold or bought around the turn of the year, that moves a version number from the appendix of a review closer to the price. What a buyer's reviewer reads, how it becomes a deal term, and what a seller can still do.Notes
· 6 min
Out of support before a sale?
Tell us about the company and the timeline. We reply within one business day.