mb-verifier

To run lint, type-check, and security scans automatically after code changes, use a quality gate that evaluates changed files in your JavaScript or TypeScript project. This ensures code meets all quality and security standards before deployment.

Architecture validation checks import boundaries and layer conventions to enforce structural rules in JavaScript and TypeScript projects. You need it to prevent architectural violations and maintain code quality when developers push changes to the codebase.

Yes, you can use this quality gate on any JavaScript or TypeScript project. It assesses changed files directly but requires your project to have existing lint tools, a TypeScript compiler, and test runners already configured to function properly.

To prevent exposed secrets and unsafe code patterns from being deployed, implement security scanning as a post-implementation quality gate. It searches changed code for vulnerabilities and blocks the release if any security violations are found.

Yes, you need to install specific test runners, lint tools, and a TypeScript compiler before using this verifier. It relies on your project's existing tools to execute tests, detect style violations, and ensure type safety across changed files.

If unit or e2e tests fail during the code quality check, the verifier flags the failures and blocks the code from progressing further in the pipeline. This guarantees that only code passing all test execution standards advances toward release.