dircue 0.6.0

Dircue 0.6.0 adds bounded file-format inspection and function hotspot distributions. Learn more about mixed directories, then select deeper source analysis where it is useful.

Inspect data and artifacts

dircue analyze formats --json /path/to/content
dircue analyze all --formats --discovery --json /path/to/content

Format evidence includes selected vendor and data files that language statistics may exclude. It distinguishes filename hints, header signatures, parsed prefixes and complete supported syntax checks. JSON, XML, UTF-8 text and empty-file checks accompany signatures for several archive, executable, document and image formats.

Reads are bounded to a 64 KiB prefix plus at most one lookahead byte per file, 32 MiB total, and 4,096 candidate files. Coverage and omissions remain visible. XML is not automatically a log; signatures do not establish archive integrity. Nothing is decompressed or executed.

Find measured structural hotspots

dircue analyze structure --hotspots --json \
  --structural-worker /path/to/dircue-structural-worker /checkout

The optional worker reuses its BCA / Tree-sitter parse to measure eligible function spaces before limiting retained evidence. Each language and clean/recovered syntax cohort gets exact fixed-bin distributions and top-ten evidence for BCA cyclomatic sums and physical line spans.

Late functions can rank even when they fall beyond the older function-list caps. Source locations, hashes, measurement definitions and missing populations accompany the results. Nested spaces may overlap; these are inspection aids, not repository grades or defect predictions.

Compare saved observations

dircue compare before.json after.json --json now supports format observations and qualified hotspot distributions. Leaving a top-ten list is not treated as function deletion. Comparison runs offline without reopening the source directories.

The new modules use aggregate schema 1.5.0 only when requested. Existing language, discovery, declaration and other profiling commands retain their contracts. Hotspots require a worker that advertises the new capability; ordinary structural commands continue to work with the previous supported worker.

Downloads

Choose the core archive for Linux or macOS on AMD64/ARM64, or Windows AMD64. Format inspection needs only that core binary. Hotspots additionally require the corresponding structural-worker archive.

Attached wheels contain the core binary for installation with Python tooling; the structural worker remains separate. Checksums, provenance and native verification receipts accompany the assets. PyPI publication remains deferred.

See the format guide, hotspot guide, and validation report for definitions, measured costs and coverage limits.