Analiz...metrics(3pm)

πŸ“¦
version 1.25.5 Β· 4 versions
, in ubuntu resolute, ubuntu stonking

πŸŽ€ analizo-metrics β€” ok so let me tell you about this one

Welcome to the analizo-metrics(3pm) page, bestie πŸ’– (yeah the manual name is a whole little ✨ Analiz...metrics(3pm) ✨ vibe, we move). This is analizo's metric reporting tool, and honestly? It ate.


πŸ’… USAGE

analizo metrics [OPTIONS] [<input>]

🌸 DESCRIPTION

So analizo metrics looks at the source code in input and gives you back a metrics report. If you don't pass an input at all, it just assumes the current directory (.) because it's chill like that.

The report it makes goes to standard output, OR you can yeet it into a file with the --output option. And the format? YAML, periodt (go look at http://www.yaml.org/ if you wanna know more about YAML, iykyk).

Also β€” important β€” analizo metrics is part of the analizo suite. It's not out here alone, it's got a whole family 🫢


✨ OPTIONS ✨

  • <input> β€” tells analizo which source code directory you want it to parse. That's it, that's the whole job.
  • --extractor <extractor> β€” picks which extractor method gets used to parse your source code. The default is Doxyparse, no cap.
    • When you're using the Doxyparse extractor (the default one), literally every file matching the languages that doxyparse supports gets processed… unless you used --language, in which case that's your filter instead. Choose your fighter πŸ’€
  • --list, -l β€” shows you the metric list. Boom, metric list, displayed.
  • --output <file>, -o <file> β€” writes the output to <file> instead of standard output. Fancy.
  • --globalonly, --global-only, -g β€” does NOT output the details about modules. Only the global (project-wide) metrics. So if you're not in the mood for per-module lore, this is your girl ✨
  • --language <lang> β€” only processes filenames that match known extensions for the <lang> programming language. Wanna know which languages are supported? Pass --language list and it'll tell you. Very demure, very mindful.
  • --exclude <dirs>, -x <dirs> β€” excludes <dirs> from the analysis, where that's a colon-separated list of directories. Super useful, for example, when you wanna focus on production code and leave the test code out of it. You'd do that by passing something like --exclude test. Chef's kiss πŸ‘‘

πŸ¦‹ OUTPUT FORMAT

The output is a stream of YAML documents, bestie. Not one document, a whole stream of them.

The first one shows the metrics for the project as a whole (main character energy). The ones that come after it show per-module metrics β€” which means there will be exactly as many of those as there are modules in your project. So if your project is huge… yeah 😭 pack a snack.


See analizo(1). That's where the credits live, go give them their flowers 🌸


ok that's the page!! ty for coming to my ted talk, go run some metrics on your codebase and slay πŸ’–βœ¨ this has been perl v5.40.1, dated 2025-12-13 β€” mwah πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from