# Composal vs Trunk Check

Trunk orchestrates source-level checks before changes land. Composal tests application behavior in a browser after a build runs, returning recordings and steps to reproduce failures.

## Composal

Composal sends AI browser agents to use your running web app and check the outcomes you care about. Define journeys as plain-English Scenarios, map existing flows with Discovery, or explore for bugs with Deep Scan. Runs keep recordings and reproduction steps so your team or coding agent can investigate a Finding.

[Verify documentation](https://composal.com/docs/verify)

## Trunk Check

Managed linters, formatters, and static checks

Trunk Check detects repository technologies and helps teams configure and manage static analyzers, linters, and formatters. It standardizes local and CI checks and keeps selected tools updated.

## What each tool does

| Workflow | Composal | Trunk Check |
| --- | --- | --- |
| [Run browser journeys](https://composal.com/product/scenarios) | ✓ Yes: Run saved browser Scenarios and return recordings and reproducible Findings. | × No: The documented product reviews or analyzes source changes; it does not execute browser journeys. |
| [Map application workflows](https://composal.com/product/discovery) | ✓ Yes: Discovery maps key application areas and user journeys. | – Not confirmed: Check whether this product includes this workflow in your intended plan and setup. |
| [Explore for unexpected issues](https://composal.com/product/deep-scan) | ✓ Yes: Deep Scan explores the running application and reports reproducible issues. | – Not confirmed: Check whether this product includes this workflow in your intended plan and setup. |
| [Describe checks in plain English](https://composal.com/product/scenarios) | ✓ Yes: Author Scenarios around the intended user outcome, then review the steps and expected results. | – Not confirmed: Check whether this product includes this workflow in your intended plan and setup. |
| [Run or inspect from a terminal](https://composal.com/product/cli) | ✓ Yes: Use the CLI to start and inspect verification runs and their Findings. | – With setup: Connect its specialist checks to your development workflow using supported integrations. |
| Source code review and analysis | × No: Use a dedicated tool for this specialist workflow alongside Composal’s browser verification. | ✓ Yes: Trunk Check detects repository technologies and helps teams configure and manage static analyzers, linters, and formatters. It standardizes local and CI checks and keeps selected tools updated. |

With setup means you supply code or configuration. Not confirmed means support for this workflow needs checking with the vendor.

## Where each fits

Choose Trunk when teams need consistent versions and configuration for many code-quality tools. Choose Composal for browser verification against product Scenarios. The tools cover source hygiene and runtime behavior.

## Try this evaluation

Enable representative lint and security checks for one repository, then run a preview with Composal after a user-flow change. Compare fast source feedback with failures that only appear during interaction.

### Coverage

Which user outcomes must this release prove, and which specialist checks must stay in your existing stack?

### Setup

Who prepares accounts, test data, permissions and access to the deployment being tested?

### Evidence

Can the engineer reproduce a reported failure from the recording and steps, without asking the tester to investigate again?

### Ownership

Who updates the checks when the product changes, and can the team review what a passing result actually proves?

## Related comparisons

- [Composal vs SonarQube](https://composal.com/compare/composal-vs-sonarqube.md)
- [Composal vs Snyk Code](https://composal.com/compare/composal-vs-snyk-code.md)
- [Composal vs Codacy](https://composal.com/compare/composal-vs-codacy.md)

[All comparisons](https://composal.com/compare.md)