Skip to content

v0.5.3

Choose a tag to compare

@LadsonDavid LadsonDavid released this 12 Nov 09:43
· 10 commits to main since this release

Much faster on big projects, with the same answers.

  • Faster first look: files are read side by side on all your cores and merged in a fixed order. On a 6,385-file project one run went from about 3 minutes to about 9 seconds (16 cores); across 39 test projects the total went from about 8 minutes to about 30 seconds. The reports are identical to the old ones. On a two-core machine expect roughly 3 to 4 times faster, not 15.
  • Read once, not twice: plain malveon used to read the whole project a second time for the "nothing reaches it" check. It now reuses the first read.
  • A saved copy between runs: if nothing malveon reads has changed (same files, sizes and times, same program build), it loads the saved map instead of reading the project. The same 6,385-file project: about 2.5 seconds. The copy lives in the cache folder of your data directory (not in your project) and holds file paths and names of functions and routes, no file text. Set MALVEON_NO_CACHE=1 to turn it off.
  • One visible difference: with --exclude, the "nothing reaches it" check now skips the excluded folders like the rest of the scan.
  • Fewer false alarms (from running the first-run scan on 100 more public projects): hand-run test-*.mjs scripts, feed/rss routes, types declared in a .d.ts, buttons inside popovers, files in public/, and more are no longer flagged.

Limits: a file changed in the last 3 seconds means that run is not saved, and any real change still rereads the whole project. The first run on files your system has not read recently can be much slower. Findings are still likely, not certain; a quiet result proves nothing.