Output Schemas
Gitquarry supportspretty, json, toon, compact, and csv.
This page documents the structured formats. --format toon serializes the same data model as JSON using Token-Oriented Object Notation, so the field contracts below apply to both JSON and TOON.
Search JSON Shape
gitquarry search --format json serializes this top-level shape:
repository.probe can include:
Search Plan JSON Shape
gitquarry search --plan --format json serializes this shape and does not call GitHub:
Inspect JSON Shape
gitquarry inspect --format json wraps one repository:
Compare JSON Shape
gitquarry compare --format json serializes this top-level shape:
tree_summary is null unless --tree-summary is active.
Tree JSON Shape
gitquarry tree --format json serializes this top-level shape:
kind is one of Blob, Tree, or Commit.
Code JSON Shape
gitquarry code --format json serializes this top-level shape:
Explain Object
When--explain is active in enhanced flows, repository.explain can include:
CSV Columns
search and inspect CSV output write this header:
topicsis pipe-delimited inside one CSV field- timestamps are RFC3339 in CSV
- score columns are
0when no explain data is present inspect --format csvwrites one rowtree --format csvwritespath,type,sizecode --format csvwritespath,line,textcompare --format csvwrites repository columns plus tree summary columns
Pretty Output
Pretty output is for humans, not strict parsing.search --format pretty prints:
- total count
- effective mode
- effective rank
- host
- per-repo summary blocks
inspect --format pretty prints:
- full name
- URL
- description
- stars, forks, language, topics, license
- dates
- archived/template/fork status
- open issue count
- latest release when available
- README block when requested
tree --format pretty prints repository/ref metadata and an indented file tree.
code --format pretty prints match counts, file paths, line numbers, and requested context lines.