Brain ScannerFree project check · JavaScript / npm
Did your agent run the whole test command?
Compare your package’s configured test lifecycle with the command your coding agent ran. Get a concrete starting point before setting up Brain Scanner.
Your file stays in this browser. No upload, account, repository access, or test execution.
Your comparison
Configured npm test lifecycle
Command you provided
Next check: compare the original task’s requirements and the command’s final exit status. A passing subcommand does not establish that the full task passed.
This reads only the package JSON you supplied. It cannot inspect CI, workspace configuration, shell behavior, flags, environment, source changes, or actual results. npm settings such as ignore-scripts can change lifecycle behavior.
Keep the evidence with your project
Brain Scanner’s free beta lets you record project context, review outcomes, and queue follow-up work with your connected coding agent. Verify your email, then connect a compatible MCP client. This local comparison is not automatically uploaded.
Create a free account See the setup stepsWhy this check exists
In our owner-run example, 23 runtime tests passed while the full npm test command failed at linting. This check helps you compare the commands; it does not certify a project.
Read the source-linked example