Rising star plugins are the ones whose score moved up rather than down, and fast growing plugins deserve a different kind of attention than the ones sliding. This post is about score momentum: how to read a dsh plugin score increase, which of the four signals usually drives it, and how to keep a rising star plugins watchlist that separates real adoption from a metadata cleanup.
What score momentum actually measures
A score recomputes from four inputs rather than being a grade you earn once. When the number climbs, one of those four moved, and which one it was decides whether the rise matters to you.
- Maintenance: last-push date, release cadence, and how long issues sit open.
- Docs: whether a README exists, how much it covers, and whether it changed recently.
- npm health: dependency freshness, and whether anything upstream went stale or was renamed.
- Security: install-script findings and supply-chain flags, either of which can move a score on its own.
The band itself is a separate question from the trend. What each band means is set out in /blog/dsh-quality-score-decoded.
Fast growing plugins: three shapes a rise takes
A jump is not automatically good news. Three patterns account for almost every rise, and only one of them means the plugin got better to use.
- A maintenance restart. A plugin that had gone quiet starts pushing again. This is the one worth acting on.
- A documentation rewrite. The README grew, so the docs signal improved while the code stayed where it was.
- A dependency refresh. Upstream packages were bumped and the npm health signal moved with them.
| Rise | Likely cause | What to do |
|---|---|---|
| +2 to +4 | Doc or metadata change | Watch one cycle |
| +5 to +9 | New release cadence or dependency refresh | Read the changelog, then try it |
| +10 or more | Maintenance restart or rewrite | Compare against the previous version before switching |
Two of those three leave the plugin exactly as usable as it was before. Only the first changes what you get out of it, which is why the size of the jump matters less than which signal produced it.
How to tell real adoption from a metadata bump
This is where a dsh plugin score increase most often gets misread. A rise in the docs signal looks identical to a rise in maintenance until you check what actually changed.
- Compare the release dates. A score that moved without a new release is almost always docs or metadata.
- Read the changelog rather than the score page. If the last entry is a README edit, you learned nothing about the code.
- Check the last-push age against the score update date. A stale push date alongside a rising score means the rise came from elsewhere.
- Look at install or star movement across the same window. Adoption and score moving together is the combination worth trusting.
Where the installs came from
The /trending page ranks by recent activity and stars, which gives you a third source to compare against. A plugin rising on score while flat on activity is a documentation event rather than an adoption one.
Score momentum tells you something changed. It does not tell you whether anyone is using the result.
Build a rising star plugins watchlist in ten minutes
A watchlist is a plain list rather than a dashboard. Mine holds eight entries and I look at it once a week, which is enough to catch anything that matters.
- List every plugin your build would fail without. That is the whole list, and it is usually shorter than you expect.
- Record the score and the band next to each one, with the date you looked.
- Add the last-push date. It is the single field that explains most movement.
- Re-check weekly. DSH Weekly at /weekly surfaces score moves across the ecosystem, so the manual pass only has to cover your own eight.
The mirror problem, scores going the other way, is at /blog/dsh-plugin-score-trends-what-a-dropping-score-means. Which plugins to look at first is at /blog/how-to-avoid-risky-dsh-plugins, and the maintenance field on its own is explained at /blog/dsh-plugin-maintenance-signals.
FAQ
- Does a rising score mean I should switch to that plugin? No. It means something changed. Read the changelog first, then decide. The comparison method is at /blog/compare-two-dsh-plugins-side-by-side.
- How fast is fast? A gain of five points or more inside one scoring cycle is worth a look. Two to four points is usually docs or metadata.
- Can a score rise for the wrong reasons? Yes. A documentation rewrite with no code change moves the number without changing the plugin itself.
- Do rising plugins need less scrutiny? No. Momentum says nothing about install behaviour. The install-script checks still apply and are covered at /blog/how-install-script-scanning-works.
Every plugin on dshquality.com carries a score page showing all four signals and the direction each one moved, so a rising star is something you can verify rather than take on trust. The activity ranking is at /trending, the weekly score digest is at /weekly, and everything published on the site is at /blog.