Code Complexity Trend Viewer
Compare supplied snapshots using documented metrics; highlight functions requiring review.
Analysis & source evidence
Load the worked example or open your own input.
Start with the worked example. Edit your input or settings, inspect the result, and open Export for task files or a complete ZIP. Save project keeps editable text and settings; image/file projects need their original source files when reopened.
Using Code Complexity Trend Viewer
Compare supplied snapshots using documented metrics; highlight functions requiring review.
- Select Try example to see a complete code complexity trend viewer workflow. Use the editable worked example as the JSON structure, or open a local JSON/YAML text fixture. File inspectors accept their stated local formats.
- Adjust the labelled controls or open Input/Geometry to change the evidence. Run workflow applies the current input; undo and redo restore text/settings decisions.
- Inspect the task preview, record details and method notes. Findings describe cases that need review; missing evidence remains unknown.
- Open Export for task artifacts, JSON/CSV results or a complete ZIP. Save project keeps input/settings; projects with local binary files need their original files to be reselected when reopened.
Example
The worked example for Code Complexity Trend Viewer produces 1 evidence records and 1 task artifacts. Uses Acorn for JavaScript modules, excluding nested function bodies from their parent count. The documented metric counts decision nodes plus logical expressions; it is not a universal maintainability score. JSX/TypeScript need precompiled JS.
Questions & answers
What does Code Complexity Trend Viewer do?
Uses Acorn for JavaScript modules, excluding nested function bodies from their parent count. The documented metric counts decision nodes plus logical expressions; it is not a universal maintainability score. JSX/TypeScript need precompiled JS.
What should I open or paste?
Use the editable worked example as the JSON structure, or open a local JSON/YAML text fixture. File inspectors accept their stated local formats. The worked example defines the supported input fields. Edit its values, run the workflow and inspect the method notes before exporting. Each selected file must be nonempty and at most 25 MiB, with at most 30 files and 80 MiB total. Image jobs use up to 12 still frames, six million pixels per image and 18 million total pixels. Individual format inspectors may apply stricter limits.
What results can I export?
The Export view includes the task-specific artifacts listed for your actual result, a typed JSON report, a CSV table and a complete ZIP. Save project stores editable input and settings; selected binary sources are represented by fingerprints and must be reselected. Secret-option values are excluded from saved projects.
Does it upload files, run commands or change a live system?
Processing uses your supplied evidence in this browser. Planners and protocol tools do not connect to services, execute imported code or apply changes automatically. Public pages include the site’s approved advertising and optional consent-based analytics.
Related tools
A useful next step for your task.
Developer & DataCode PlaygroundFull workspaceWrite HTML, CSS and JavaScript online with a live preview and console. Multi-file projects, syntax highlighting, phone/tablet preview, templates,…
Developer & DataGit Patch InspectorReview changed files, additions, deletions, hunks and binary markers without applying a Git patch.
Developer & DataPairwise Test Scenario GeneratorCover factor pairs with constraints; compare coverage; export reproducible test matrices.
Developer & DataImport Path Migration AssistantMap moved files; preview import rewrites; export patches with unresolved references.
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.