Latest
What You Have to Decide Before Anybody WritesWriting It Before You Need ItCross Training Covered Everything Except the Role That Mattered MostBehind the Book: You Don’t Own Anything AnymoreBehind the Book: The Woke VirusBehind the Book: Galactic InvasionWhat’s New at The Writing King: Week of November 8, 2026Alexander Zhidkov: Decision MakingJessi Szurek: Expand Your RangeYou Don’t Own Anything AnymoreThe Budget Decided How My Department Was ShapedWhy Your Competitor’s Book Is Working and Yours Would NotWhy Are These Guys Smiling? A Business Book That Became a Wrestling MemoirPangram Wants to Decide Who Gets PublishedWhat You Have Enough Material For Right NowWhen a Book Is the Wrong ToolThe Woke VirusGalactic InvasionChatGPT Turns Four: From a Free Research Preview to GPT-6What’s New at The Writing King: Week of November 1, 2026Diwali: The Festival of Lights and the Story Behind the LampsHow Much Water and Power Does Heavy AI Use Take? I Ran My Own NumbersBad Boys: Ride or Die (2024)Vesuvius Day: The Teenager Who Wrote Down Pompeii’s Last DayAnti-Communism Week: Remembering the Writers Communism SilencedVoyager 1 One Light-Day: Fifty Years to Travel One Day of LightVellum Added an Optional AI Feature. A Pile-On Killed It in a Day.Are AI Subscriptions Losing Money? The Gym Membership Math Says NoAI Terms Every Writer Should Know, and Why Each One MattersWorking While Sick: What 24/7 On Call Cost MeHe Banned AI From His Writing Group. His Own Cover Got Called AI Slop.Who Writes the Fake Fan Mail Authors Get? Inside the Scam CompoundsSMS Appointment RemindersJoe Rockey: Ghostwriting His BookDarrell Stern: Stop Being Invisible, Become UnmissableFree BooksHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own Fault
The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

The Single Maintainer Problem: Who Keeps Your Software Alive?

TL;DR: Before installing any software, ask the question nobody asks: how many people keep it alive? The number is public, takes five minutes to find, and predicts more grief than any feature list. My favorite theme was one brilliant developer. That means one bus, one burnout, or one sale away from abandonment. That math changed what runs on my sites.

Before I install anything now, I check how many people maintain it, a different number from how many people use it.

A story about one man and a great theme

For years my fiction site ran on Fictioneer, and I’ll repeat what I said earlier in this series: it’s an excellent theme, the best tool that exists for running serial fiction on WordPress. Its developer, Tetrakern, built something the big commercial shops never bothered to build, and built it with obvious love. Reading the code, you can feel a single coherent mind at work, and that’s the quality the Frankenstein themes from the assembly lines lack.

And that’s the problem. A single coherent mind is one mind. One person to fix bugs, one person to chase compatibility with every new WordPress release, one person to answer the support threads, one person between the theme and abandonment. Following the project over time, I noticed the small signals anyone can learn to read: releases still coming, bugs still fixed, and alongside them, the occasional weary comment from a maintainer who plainly loves the work and just as plainly carries all of it alone.

Nothing about the project was failing. This is a story about arithmetic.

Because I’d built a serious part of my business on those custom structures, my content had grown around the theme the way content does. Which meant my fiction platform’s future was, in a real sense, one person’s hobby energy. No malice required, no failure required. A new job, a health problem, or simple burnout, and the software holding my stories would begin drifting out of compatibility, one WordPress release at a time.

I left, eventually, for exactly that reason, and it remains the most respectful divorce I’ve ever conducted. The theme was excellent. The bus factor was one.

What is the bus factor in software?

Engineers call it the bus factor: how many people would have to be hit by a bus before the project dies. It sounds morbid because it is, and it’s the single most underrated number in software selection.

A bus factor of one is the norm. The directory is full of beloved plugins and themes maintained by one person in their evenings, and most of the time that works, until the evening they stop. Abandonment is rarely announced. It looks like an update that never comes, then a compatibility warning, then a security advisory nobody patches. (See also why AI companies should pay to keep PHP alive.)

The worst part is who ends up holding the bag. The maintainer burns out after years of unpaid evenings, the site owner learns about it from a security advisory, and the plugin can sit in the directory looking perfectly installable long after anybody’s home. Nobody in that chain did anything wrong on purpose, and the damage lands anyway, usually on the smallest sites with the least help.

And an unmaintained plugin isn’t merely stale; as my own incident showed, orphaned and sold projects are exactly how attackers acquire trusted channels into hundreds of thousands of sites.

Checking the number takes minutes. Look at who publishes the software and whether that’s a person or an organization. Look at the changelog: steady releases across years, or a burst of energy followed by silence? Read the support forum: are questions answered, and by whom, and in what tone? A maintainer answering every thread personally is admirable and is also a bus factor of one introducing himself.

Checking a tool's bus factor in three looksThree checks that reveal how many people keep a piece of software alive. Look at who publishes it and whether that is a person or an organization. Read the changelog for steady releases or a burst followed by silence, then read the support forum to see whether questions get answered, by whom and in what tone.Checking a tool's bus factor in three looks1PublisherA single person or an organization?2ChangelogSteady releases across years, or aburst then silence?3Support forumAre questions answered, by whom,and in what tone?
Checking a tool's bus factor in three looksThree checks that reveal how many people keep a piece of software alive. Look at who publishes it and whether that is a person or an organization. Read the changelog for steady releases or a burst followed by silence, then read the support forum to see whether questions get answered, by whom and in what tone.Checking a tool's bus factor in threelooks1PublisherA single person or an organization?2ChangelogSteady releases across years, or a burst thensilence?3Support forumAre questions answered, by whom, and inwhat tone?

Three public checks that show how many people stand between a plugin and abandonment.

The gradient, revisited

Now combine this with the lock-in gradient from the page builder article, because the two multiply.

A maintainer answering every thread personally is admirable and is also a bus factor of one introducing himself.

A shallow tool with a bus factor of one is a small risk: if it dies, you swap it in an afternoon. (See why I trust a young Word clone with my manuscripts.) An embedded tool with a bus factor of one is a different animal entirely. That’s your content grown around a fence post that one person maintains. The deeper the embedding, the more the maintainer count matters, until at the deepest end, the full builders and platforms, you should be reading the vendor’s staffing the way you’d read a landlord’s finances.

This cuts against instinct, because the embedded tools feel safest. They’re polished, popular, everywhere. But popularity only measures adoption, and even big teams sell catalogs, pivot, or fold. The question is who’s contractually, financially, or emotionally bound to keep it good in year five.

I think the whole review industry trains people to ask the wrong question. Comparison posts line up features and star ratings, and almost none of them tell a small business owner to check whether one tired person stands between their site and the next security hole. That omission costs people their sites, and it would take a reviewer five minutes to fix.

My take

Check how many people keep a tool alive before you install it. Five minutes in the changelog and the support forum tells you. A bus factor of one is fine for a shallow plugin you can swap in an afternoon. For a builder your whole site grows around, it’s a serious risk. A popular tool can still have one maintainer, and a big team can still sell the product off. Ask who’ll still be bound to keep it good in year five.

What should you do about a low bus factor?

I’m not telling you to boycott solo developers. Some of the best software in the world is one person’s obsession, and Fictioneer proves it. I’m telling you to price the number in.

For shallow tools, a bus factor of one is fine. Enjoy the craftsmanship.

For anything embedded, demand a higher number or a proven exit. Either multiple maintainers with an organization behind them, or software that stores your content in structures that survive its death. One or the other. Insisting on both is how the cautious sleep.

For everything already on your site, check the pulse yearly. The maintainer situation that was healthy at install has had years to change, and the check costs five minutes per plugin. The annual audit from the previous article is the natural place for it.

And when you find a beloved tool with a bus factor of one holding something your business depends on, do what I did: thank the maintainer sincerely, and start planning your independence while everything is still working. The worst time to leave is after the last update never arrives.

How to handle bus factor by situation
Situation Risk What to do
Shallow tool, one maintainer Small; swap it in an afternoon Enjoy the craftsmanship
Embedded tool Your content grows around one person’s fence post Demand multiple maintainers or content stored in structures that survive
Everything already installed The maintainer situation has had years to change Check the pulse yearly, five minutes per plugin
Beloved one-person tool your business depends on Abandonment arrives unannounced Thank the maintainer and plan independence while it still works

Next in the series: the update channels themselves, and how attackers stopped breaking into websites and started buying the roads that lead to them. That story, including the hostile computer that can hide inside a cable, is The Supply Chain Is the Attack Surface. And if you want an experienced eye on the bus factors holding up your own site, that’s work I do.

Frequently Asked Questions

Why does the bus factor matter when choosing software?
Because it measures how many people would have to be hit by a bus before a piece of software stops being maintained. I think of it as the single most underrated number in software selection, because it predicts more grief than any feature list. A bus factor of one is the norm in the WordPress world, and the plugin directory is full of beloved tools kept alive by one person working evenings. I learned this firsthand with the Fictioneer theme, which was built entirely by one developer, Tetrakern, with obvious love and skill. That single coherent mind made the theme excellent, but it also meant one person stood between my fiction platform and abandonment.
How do you check who maintains a WordPress plugin or theme?
The information is public and takes five minutes: the plugin’s repository, its changelog, the developer’s site, the commit history. How many names appear? How recent is the activity? That number predicts more grief than any feature list.
Is it safe to use software with a single maintainer?
It can be, with eyes open. Some of the best tools are one brilliant developer’s work, and that’s the risk: one burnout, one career change, or one sale of the project away from abandonment. Plan the exit before you need it.
What happens when a plugin developer abandons a project?
Abandonment is rarely announced, so I watch for the quiet signs instead. First the updates stop coming, then a compatibility warning appears, and eventually a security advisory shows up that nobody patches. I learned through my own incident that orphaned or secretly sold plugins are exactly how attackers acquire trusted channels into hundreds of thousands of sites. An abandoned plugin is a countdown toward a break or a security hole, and I now check the pulse of every plugin I rely on once a year for exactly this reason.

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment