--
title: "CI/CD Plugin Scanning: Adding DSH Checks to Your Pipeline"
description: "Plugin quality checks should run on every push, not in a quarterly review. This is how to wire DSH scoring into a CI/CD pipeline."
tags: ["ci-cd", "plugins", "quality", "automation"]
canonical_url: https://dshquality.com/blog/ci-cd-plugin-scanning
CI/CD Plugin Scanning: Adding DSH Checks to Your Pipeline
Plugin quality checks should run on every push, not in a quarterly review. This is how to wire DSH scoring into a CI/CD pipeline.
Why this matters more than it looks: Plugin quality drifts silently. A plugin that scored well last quarter can fall below threshold after one dependency bump, and nothing surfaces it until something breaks in production.
How to approach it: Add the scan as a required check on the default branch only. Fail the build on a score drop rather than on an absolute threshold, so existing debt does not block unrelated work.
The most common mistake here is copying someone else's checklist wholesale. Their constraints are not yours, and the parts that do not apply will quietly push you toward decisions you would not otherwise make. Use any checklist to confirm you have not forgotten something — not to decide what to do.
The full version, with the order of operations and the details that do not fit here, is on the original post: https://dshquality.com/blog/ci-cd-plugin-scanning
Top comments (0)