heal.dev runs an application in a production-like sandbox to identify reproducible bugs, runtime vulnerabilities, and performance issues, with evidence such as failing tests and reproduction steps.
What the product does and how it is positioned
heal.dev examines a repository, maps the application's architecture, and builds a sandbox that represents the application environment. It then runs flows and investigates behavior, security, and performance issues.
Reports describe the observed situation, expected result, failed screen, reproduction path, relevant code location, and a test that reproduces the defect. External services that cannot run in the sandbox are mocked or emulated.
Source-supported ways to use the product
Teams can use runtime checks across the whole product before a release or on a recurring schedule.
The sandbox exercises flows involving payments, mail, and third-party services with failing, slow, or repeated responses.
Security teams can review vulnerabilities that are reproduced by exploits against the sandbox.
The product crawls the running application to identify missing routes, dead pages, and assets that do not load.
The documented workflow, where available
Heal reads the repository and maps the application's architecture, features, routes, and screens.
It creates a production-like environment using application components, test data, and mocked or emulated dependencies where needed.
Heal runs application flows and investigates behavior, security, performance, edge-case, and integration conditions.
The system files a defect only when a test reproduces it and supplies the failing test and supporting evidence.
heal.dev distinguishes a suspected issue from a filed defect by requiring reproducibility. Its reports can show what happened, what should have happened, the affected screen, the reproduction sequence, and where to investigate in the code.
Checks to run with your own material and workflow
What was checked and when
Answers based on the source-checked product record
The official product description says heal.dev analyzes a running product, its features, data, and called services, in addition to reading the repository.
A report can include the situation, actual and expected behavior, failed screen, reproduction steps, code location, captures, and a failing test.
Payments, mail, and third-party APIs can be mocked or emulated in the production-like sandbox, with responses replayed as failing, slow, or repeated.
Yes. The source says it runs security exploits against the sandbox and reports security issues that are reproduced by a test.
The official site states that the product can run locally or in the cloud, and that a repository can be connected through GitHub.
