completeness-gate

To scan JavaScript code for placeholder patterns, run a completeness-gate scan across stores, components, utilities, and tests. It detects incomplete implementations using 12 checks like placeholder-returns, empty-function-bodies, and hardcoded-sample-data, generating a structured JSON report with file:line references.

Before deploying TypeScript code, check for production readiness anti-patterns like not-implemented-throws, todo-fixme-comments, empty-catch-blocks, log-and-return, noop-handlers, console-log-leftovers, three-state-ui, unwired-store-actions, and artifact-verification issues. The scan reports findings with severity levels.

Yes, you can use a completeness gate to generate a CI dashboard report for code readiness. The scan outputs a structured JSON report containing severity, file path, and line references for production readiness issues found across your codebase.

To suppress false positives during static analysis for production readiness, use a .completeness-gate.json override configuration file. This allows you to suppress known false positives while preserving the audit intent of the codebase findings.

Yes, the completeness gate scan works for both JavaScript and TypeScript projects. It applies static analysis checks across stores, components, utilities, and tests to identify incomplete implementations and production readiness issues in both language ecosystems.