codapult-guard
OfficialRelated Servers
Alternatives to codapult-guard
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceArchitectural Gatekeeper for AI coding. Prevents "tunnel vision" bugs by forcing the AI to verify dependencies (via AST parsing) before editing files. Supports JavaScript & TypeScript. Blocks unsafe edits until the AI proves it understands the impact3Apache 2.0
- AlicenseAqualityBmaintenanceFast architectural linter & guardrail engine for AI coding agents. Detects layer violations, leaked secrets, and enforces .cursorrules & CLAUDE.md standards in ~12ms.4217 npm5MIT
- AlicenseAqualityCmaintenanceGuardrails for AI coding agents that enforces rules via compliance receipts, blocking destructive actions and syncing rules across all AI tools.24145 npm1MIT
- AlicenseAqualityDmaintenanceEnforces AST-based architectural guardrails on AI-generated code, blocking writes that violate maintainability, security, or complexity rules and prompting immediate refactoring.2MIT
- FlicenseNot gradedqualityCmaintenanceReal-time architecture governance tool that enforces Clean Architecture, DDD, SOLID, TDD, and Security rules across 8 languages using 11 specialized agents.-
- AlicenseNot gradedqualityBmaintenanceIt enables AI coding agents to deterministically analyze TypeScript, React/Next.js, and Python code via AST parsing, tracing data flow, exposing hidden state leaks, and validating cross-boundary contracts with compact, token-efficient JSON. It also supports architecture rule auditing and drift detection between Git baselines and working trees.MIT
TDQS
Scored across 14 tools
The tools cover distinct workflow stages, and descriptions explicitly contrast check vs audit vs verify vs review. Some overlap remains among policy-checking and orchestration tools such as next_action, check, audit, verify, and review, but boundaries are mostly clear.
All names share the codapult_guard_ prefix and snake_case formatting, which is highly consistent. However, suffixes mix verbs and nouns such as analyze, context, proposal_decide, and waivers, so it is not a pure verb_noun pattern.
Fourteen tools is within the well-scoped range for a multi-stage governance workflow. Each tool maps to a distinct lifecycle operation, and the set does not feel bloated for the apparent domain.
The surface covers initialization, discovery, context inspection, proposal and decision handling, checks, audit, semantic review, verification, waivers, governance, impact analysis, explanation, and next-action orchestration. No obvious lifecycle gap is apparent; even replacement is handled through init with force.