--
title: "30 Days of DSH Quality Data: What the Numbers Actually Show"
description: "Title: 30 Days of DSH Quality Data: What the Numbers Actually Show Excerpt: 30 days of dsh plugin quality data, sorted by cause: which signals move sc"
tags: ["30-days-of-dsh-quality-d"]
canonical_url: https://dshquality.com/blog/30-days-of-dsh-quality-data
Title: 30 Days of DSH Quality Data: What the Numbers Actually Show
Excerpt: 30 days of dsh plugin quality data, sorted by cause: which signals move scores, how to read plugin quality data without over-fitting, and the three numbers to check before you install.
Meta description: 30 days of dsh plugin quality data: how to read plugin quality data, what dsh plugin score trends over time reveal, and the dsh quality data points worth checking before install.
30 days of dsh plugin quality data is enough to show which signals actually move and which ones only look like they do. We took every score recorded on dshquality.com between 2026-09-26 and 2026-10-26 and sorted the changes by cause. Here is how to read plugin quality data without over-fitting to one grade, what dsh plugin score trends over time say about maintenance, and which three numbers matter before you install anything. dsh quality data is noisy at the edges, so the direction counts for more than the decimal.
What 30 days of scanning actually produced
Between 2026-09-26 and 2026-10-26 the scanner recorded 1,180 score updates across 390 plugins. Most of the updates were small. The useful part is which signal caused each one.
Repo activity dominates, and it pushes in both directions. A plugin that ships a release tends to gain. One that goes quiet tends to bleed a point or two a week.
- Signal: Share of changes, What it usually means
- Repo activity (commits, releases): 41%, Maintainer still shipping, score drifts up
- Install script changes: 23%, Re-scanned, grade can drop in a single day
- Documentation edits: 18%, Small movement, usually one or two points
- Dependency updates: 12%, Mixed, can move either direction
- Stale repo, no commits and no releases: 6%, Slow decay, the most reliable downward signal
Three numbers worth checking before you install
You do not need the whole report. Three numbers answer most of the question.
- The grade, plus the gap to the next grade. A B sitting at 89 and a B sitting at 76 are not the same risk.
- Days since the last release. Under 30 is healthy. Over 180 means you are adopting code that nobody is watching.
- How many install script signals are open. One is worth reading. Three is worth a conversation with your team.
If you want the full piece, it is here: https://dshquality.com/blog/30-days-of-dsh-quality-data
Top comments (0)