Help for owners
My app runs on libraries that have not been updated for a long time
Short answer
Apps are built from many third-party packages. When they are not updated, known security problems stay in your product and each later upgrade becomes bigger and riskier. The safe approach is an inventory, small updates in order with tests, and a plan for packages that are no longer maintained.
Does this sound like your situation?
- My developer says it cannot be upgraded because everything would break.
- A security scan or an insurer flags old components in my app.
- The app only builds on one old computer with old tools.
- A store, host or payment provider has warned that something I rely on is being retired.
- Adding a small feature takes much longer than it should.
Why does this happen?
Updates were postponed because nothing was visibly wrong
An app that works gives no reason to touch the packages under it. Each postponed update widens the gap and makes the next one harder.
Packages depend on each other
Updating one library often needs another to move too. A long gap turns a one-step update into a chain of linked changes.
Some packages are abandoned
Maintainers stop working on some libraries. They no longer get security fixes, and the app needs a replacement, which is real work.
No tests protect the update
Without automated checks, every update needs someone to try the whole app by hand, so the team avoids it.
The build only works in one setting
When the app is built with old tool versions on one machine, a newer tool breaks it and the team keeps the old setup alive.
What can I do about it today?
- Ask for a list of what the app usesAsk for a plain list of the main packages, their versions and which ones are no longer maintained. The developer can produce it from the project files.
- Ask which are security-relatedAsk which outdated items have known security problems, and which ones touch logins, payments or customer data.
- Do not update everything at onceA big-bang update is the riskiest option. Ask for a staged order, with a backup before each step.
- Check that the build works from the repositoryAsk someone to build the app on a clean computer from the stored code. If that fails, fix it first.
- Keep a copy before any changeMake sure there is a working backup of the live app and its data before updates begin.
When should I bring someone in?
- An insurer, auditor or customer has asked about old components and you cannot answer.
- Your developers say the app cannot be updated at all.
- A package that handles payments or logins is no longer maintained.
How do I handle it?
- Make the inventoryI list the packages and tools, mark which are outdated, unmaintained or security-relevant, and rank them by risk.
- Add a safety net firstBefore updating, I make sure the key flows have checks, and that a backup and a way back exist.
- Update in small stepsOne group of related packages at a time, tested and released, instead of one large jump.
- Plan replacementsFor abandoned packages, I propose a replacement and say what it will cost in effort before starting.
- Set up a rhythmA regular small update keeps the gap from growing again.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is an old library always dangerous?
No. The risk depends on whether it has known problems, whether it is exposed to the internet and what it handles. That is what the inventory finds out.
Can I just leave it because it works?
For a time, yes. The cost is that the longer it waits, the larger and riskier the eventual update will be.
Will updating break my app?
It can. That is why updates are done in small steps with checks, a backup and a tested way back.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.
For your developer: the technical fixes
create-react-app is deprecated.npx create-react-app prints a deprecation message or will not set up a new projectYour lock file does not contain a compatible set of packages. Please run composer update.composer install says the lock file is not compatible and asks for updateIncompatible peer dependencies found.ng update stops on peer dependency errors when moving to a much newer Angular