No user-submitted related servers found.
Scored across 15 tools
The crowded audit_* family (audit, audit_bulk, audit_project, audit_deep, audit_workspace) could trip up an agent, but descriptions explicitly scope each one (single package vs. project vs. transitive tree vs. workspace files vs. bulk array). The verify/score/guard trio is also well-graded by depth. Minor residual overlap between audit_bulk and audit_project keeps this from a 5.
All tools share a consistent depguard_ prefix and snake_case style, which reads predictably. The only deviation is mixing verbs (audit, verify, guard) with nouns (sbom, exposure, sweep, score), but the convention is uniform enough to be unsurprising.
15 tools sit squarely in the well-scoped 3-15 band. Each tool covers a distinct capability (audit, SBOM, exposure scan, remediation, recommendation, search, verify, sweep, review) so none feel redundant at the count level.
The surface covers the full dependency-security lifecycle: discovery (search/should_use), pre-install gating (guard/verify), auditing (audit/project/deep/bulk), incident response (exposure), reporting (sbom), cleanup (sweep/review), and remediation planning. The only gap is that remediation is read-only (no apply/fix operation) and there is no standalone license-compliance tool, but these are reasonable scoping choices.