Skip to content

FAQ

No. denoise reads the code with a parser and draws what it finds. The same code always gives the same drawing, and nothing in it is a guess. It does not say a change is good or bad. It shows you what changed so you can judge. See What is denoise.

A function’s cognitive score is green at 5 or less, amber from 6 to 15 and red above 15. On the component map, a component is calm when it has 8 or fewer cognitive points per 100 lines of code, warm up to 16 and hot above. Inside a schematic, the fill warms as blocks nest deeper. See Metrics and Reading a schematic.

denoise reads JavaScript, TypeScript, Python, Go, Java, Kotlin and C#. Files in other languages are listed but not drawn, and the app tells you when most of a folder is one of them. See Languages and limits.

A file is skipped when it is larger than 1 MB, when it sits in a folder like node_modules, dist or vendor, or when it is minified or generated. Very large folders are cut to the first files too. See Languages and limits.

A link carries its own zoom when it was copied from the app. Without one, a pull request, commit or comparison opens at Schematic, to show the structure of what changed. A repository, folder or file opens at Headers, to show where the complexity is. After you choose a zoom, the app remembers it. See Using the app.

Public code is read by the server and its drawings are cached by commit. Private code is read in your browser with your own GitHub token and never reaches the server. See Private repositories and privacy.

Sign in with GitHub, and make sure the denoise GitHub App is installed on that repository. The app can only see the repositories you chose. See Private repositories and privacy.

Yes. The denoise, denoise-fn and denoise-data commands run on your machine, and an MCP server is available for agents. See CLI, JSON and MCP.

A schematic taller than 3,000 pixels folds its deepest blocks so it fits. Open a fold to see inside, or turn on “Don’t collapse huge functions”. See Languages and limits.