ON
SOFTWARE

Onefetch 2.27.1 Git Repository Statistics for Windows

A local Git repository summary tool that shows languages, code volume, commits and authors in a terminal, with configurable fields and JSON or YAML output.

Version 2.27.1Windows x64MIT; verify the included license and current project terms before redistribution

What Onefetch shows

Onefetch summarizes a local Git repository in the terminal: languages, code volume, commits and authors can be displayed in a compact project overview. Fields, ignored paths and output style can be adjusted, while JSON and YAML output make a repeatable report easier to process.

Keep the measurement comparable

The visible language summary depends on the selected categories, ignored directories, generated files, submodules, untracked content and Onefetch version. Prose and data formats such as Markdown, JSON and YAML may be hidden by the default view. Record the version, parameters and date before comparing repositories or releases.

Review Git identity data

Author statistics come from Git names and email addresses. Multiple identities can be mapped with a repository .mailmap, but the mapping should be reviewed with the repository maintainer before use. Screenshots and structured output may expose private repository names, people and commit patterns; redact them before sharing.

File scope

The indexed file is a 6.07 MB Windows x64 installer for Onefetch 2.27.1. Content review date: 2026-08-23.

SAVE TO CLOUD

Save to your cloud drive

Open the cloud drive to get the file directly, or save it for convenient access on another device.

Links checked 2026-08-06
Save first, access when you need itOn desktop, scan with the matching cloud-drive app. On mobile, tap the save button.
GUIDE

Onefetch Windows Git repository statistics guide

Start with a public or fictional test repository, verify the fields and measurement scope, then export structured output only after checking identity and repository details.

Before you start

  • Prepare a local Git repository with readable history and working-tree files.
  • Use a public or fictional repository for the first run and keep private project output local.
  • Record the Onefetch version, ignored paths, language categories and treatment of untracked files.
01

Installation steps

  1. 01

    Run the Windows installer

    Check the filename, architecture and version of onefetch-setup.exe, install it and open a new terminal to inspect the help and version output.

  2. 02

    Verify the repository path

    Run a Git status check in a test repository and confirm that the path contains readable .git history rather than only an exported source snapshot.

  3. 03

    Save a baseline

    Keep the default view first, record the date and save a local note before changing language categories, ignored paths or output format.

02

Quick start

  1. 01

    Analyze the current repository

    Enter the repository root, run Onefetch and compare the project name, languages, code volume, commits and author summary with local Git data.

  2. 02

    Analyze a specified path

    Pass a repository path from another directory and confirm that the target path, rather than the current or parent repository, is being read.

  3. 03

    Export structured output

    Use the help to select JSON or YAML output, write it to a new local file and inspect encoding, fields, project names and author data before scripting it.

Usage tips

  • Fix the version, language categories, ignore rules and history scope before comparing results over time.
  • Review a `.mailmap` identity mapping with the repository maintainer so different people are not merged accidentally.
  • Redact private repository names, author emails and commit details from terminal images and JSON or YAML files before sharing.
Troubleshooting and uninstall

Why does Onefetch say the path is not a Git repository?

Check that the path contains readable .git data; an archive or source export usually has no history, so use a complete local clone or limit the report to file statistics.

Why does the language ratio differ from another tool?

Compare prose and data categories, generated directories, submodules, untracked files, ignore rules and the exact Onefetch version before interpreting the difference.

  1. Remove Onefetch and exported reportsUninstall it through system app management, remove its program directory from PATH if needed and review local JSON or YAML reports before archiving or deleting them.
FAQ

Frequently asked questions

Does Onefetch need an internet connection to analyze a repository?

Core analysis reads local Git history and files. Installation, updates or opening other links may still use the network.

Why might Markdown, JSON or YAML be absent from the language summary?

The default view emphasizes programming and markup categories; include prose or data categories explicitly when those formats matter to the comparison.

Why does one author appear more than once?

Different names or email addresses in Git history create separate entries. Review and maintain a `.mailmap`, then run the report again.

What format and version is the indexed file?

It is a 6.07 MB Windows x64 installer for Onefetch 2.27.1; verify the filename and version after downloading.