Watching a dsh score trend is the cheapest early warning you get. When a plugin you depend on shows a plugin score decline, that number usually moves before the bug reports do. I keep a short watchlist plugins list for the tools my team relies on, and I check it whenever a score shifts by more than a few points. This post shows what a dropping score means, how to read the trend, and when to act.
What a dsh score trend actually shows
A score is not a grade you earn once. It recomputes from four signals: maintenance, docs, npm health, and security. A dsh score trend that points down is telling you one of those signals changed, not that the plugin author became a worse person overnight.
The useful part is the slope. A single-point dip after a big release is noise. A steady slide across three score updates is a signal.
Reading a plugin score decline without panic
Before you rip a plugin out, ask what changed. A plugin score decline of two or three points after a README rewrite is normal. The same drop after a new dependency appears in the tree deserves a look.
- Check the maintenance field. A stale last-push date is the most common cause.
- Check npm health. An unmaintained or renamed dependency drags the score.
- Check security. A new install-script flag can drop a band on its own.
- Check docs. A deleted README removes the documentation signal entirely.
Build a watchlist plugins routine that takes five minutes
You do not need a dashboard to start. A watchlist plugins routine is a plain list you glance at each week. I keep mine in a note next to the build server, and I add any plugin my team would miss if it broke.
The DSH Weekly digest (/subscribe) does part of this for you by surfacing score moves across the ecosystem. Pair it with a manual scan of your own short list and you will catch most problems early.
What a dropping score usually points to
Most drops trace back to one of four things. None of them are mysterious once you know the inputs.
| Signal | What a drop here means |
|---|---|
| Maintenance | Last push is stale; the plugin is cooling off |
| Docs | README shrank or vanished; new users get no onboarding |
| npm health | A dependency went unmaintained or got renamed |
| Security | A new install-script or supply-chain flag fired |
Two of these four are quiet. Docs and npm health slide without anyone noticing until the score moves.
A short comparison of score moves
Not every move means the same thing. Here is how I sort them.
| Move | Likely cause | Action |
|---|---|---|
| -2 to -4 | Cosmetic doc or metadata change | Watch, no change |
| -5 to -9 | New dependency or stale push | Review before next update |
| -10 or more | Security flag or broken bundle | Switch or pin now |
When to act on a falling score
A dsh score trend only matters if it changes what you do. I act when a plugin I ship to users crosses a band (say B to C) or picks up a security flag. Below that, I note it and move on.
If you need to compare options before switching, the score breakdown at /blog/dsh-quality-score-decoded shows exactly how each band is built. And before you install a replacement, the scanner write-up at /blog/how-install-script-scanning-works explains what gets flagged.
FAQ
Q: How often should I check my watchlist plugins? A: Once a week is enough for most teams. Tie it to your DSH Weekly read so the habit sticks.
Q: Is a dropping score always bad? A: No. A small dip after a docs change is normal. A band change or a security flag is the part to respect.
Q: Can a score go back up? A: Yes. Fix the stale push, restore the README, or drop the bad dependency and the next recompute can recover the points.
About DSH Quality
DSH Quality scores every plugin on maintenance, docs, npm health, and security, so a dsh score trend in your watchlist is built on evidence, not opinion. See the current rankings at dshquality.com, read how the score is computed, or browse the full plugin index at /.