Automated npm Package Maintenance Reviews
Every Monday, WebRun signs into npm, reviews each package you publish for how long since the last version, whether the readme, repository link and licence fields are complete, and whether any deprecation notice is showing, opens a Trello maintenance card per package that needs work, and sends you the summary on WhatsApp.
How do I keep my published npm packages maintained?
WebRun signs into npm every Monday and reviews each package you publish for stale versions, missing readme, repository or licence fields, and deprecation notices. It opens a Trello maintenance card per flagged package with its download figure and sends you a WhatsApp summary of what needs work.
- Stale packages surface every Monday rather than after a bug report
- Missing readme, repository, and licence fields get caught and ticketed
- The most downloaded packages get fixed first
Built for open source maintainers · JavaScript developers · platform teams · engineering leads
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.npmjs.com/loginin a real browser with your saved login - no setup, no API keys. -
1
npm - review your published packages
npmjs.com
WebRun opens npm to review your published packages. - Sign into npm and open the list of packages you publish
- For each package read the latest version, its publish date, and the weekly download figure
- Check the package page for a readme, a repository link, a licence, and any deprecation notice
- Flag packages with no new version for more than 6 months or a missing metadata field
- Only read. Never publish a version, deprecate a package, or change access
Done when Every published package has a last-publish date and a metadata check.
-
2
Trello - open a maintenance card
trello.com
WebRun opens Trello to open a maintenance card. - Open your maintenance board in Trello
- Create one card per flagged package named for the package and the reason it was flagged
- List the missing fields and the months since the last publish in the description
- Add the weekly download figure so the busiest packages can be prioritised
- Update rather than duplicate a card that already exists, and archive cards for packages now healthy
Done when Every flagged package has one current Trello maintenance card.
-
3
WhatsApp - send the weekly summary
whatsapp.com
WebRun opens WhatsApp to send the weekly summary. - Send yourself a short weekly summary on WhatsApp
- Show how many packages are healthy and how many were flagged
- Name the three flagged packages with the highest download figures first
- Send a single all-clear line when nothing needs attention
Done when You have this week's package maintenance summary in WhatsApp.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it publish or deprecate a package?
No. WebRun only reads your npm package pages. It never publishes a version, deprecates a package, changes access, or edits any package setting. Every release stays a manual action.
What makes a package get flagged?
No new version for more than six months, or a missing readme, repository link, or licence field, or a deprecation notice showing on the page. You can change the staleness window.
How does it help me prioritise?
Each Trello card carries the package's weekly download figure, and the WhatsApp summary names the three most downloaded flagged packages first, so the widely used ones get attention before the quiet ones.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.