Safeguard
Security Guides•

What does end of life mean for software? EOL, deprecated, unmaintained

End of life means a vendor stops patching. Learn how it differs from deprecated, end of sale and unmaintained, and which one signals real security risk.

Safeguard Security Team
3 min read

End of life (EOL) means the maker has stopped providing updates, including security fixes, for a specific version. The software keeps running, but newly found flaws stay open. It differs from deprecated, which is a warning, and from unmaintained, which describes a project nobody updates.

Terms people mix up

These words get used interchangeably. They describe different situations.

TermWhat it meansSecurity fixes continue?
End of life (EOL)The maker has set a date after which a version gets no updatesNo, after the date
End of supportUsually the same as EOL, sometimes only ends help desk supportCheck the vendor wording
End of saleThe product can no longer be boughtOften yes, for a while
DeprecatedThe maker advises against use, and plans removalUsually yes, until removal
Unmaintained or abandonedNobody is updating it, often with no announcementNot reliably
Extended supportPaid or limited coverage after standard supportYes, often only Critical issues

The Windows 10 case shows the wording. Microsoft's FAQ says that after end of support there are no quality updates, security fixes or technical support, and that the paid ESU program covers only Critical and Important security updates.

Why the difference matters

A deprecation warning, such as an npm message, tells you to plan. It is not an emergency. An EOL date tells you when plan becomes risk. An unmaintained project has no date at all, which makes it the hardest to track. See what to do with an npm deprecated warning and how to tell if a dependency is abandoned.

What actually changes on the date

Nothing breaks. The software runs as before. What changes is the flow of fixes. Any vulnerability disclosed afterwards is not patched, and attackers can read the public details. Compatibility also erodes, since browsers, libraries and hardware drop support for old versions.

Steps to handle an EOL notice

  1. Identify what you run. You cannot act on what you cannot see.
  2. Find the vendor's own date, not a third party summary. Use the summary to find it, then confirm.
  3. Assign an owner and a decision: upgrade, extend, isolate or retire.
  4. Record exceptions with a review date.
  5. Recheck on a schedule, since dates move.

Quick check

Is EOL software automatically vulnerable?

Not automatically. It may have no known open flaws today. It has no path to a fix if one appears, so risk grows with time.

Is deprecated the same as end of life?

No. Deprecated is advance notice. EOL is the date the fixes stop.

Where Safeguard fits

Safeguard's SBOM and dependency scanning gives you the inventory that these decisions depend on, and policies and gates can turn your own rules into checks on pull requests. See the free scan.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.