dustin/go-humanize

Go Humans! (formatters for units to human friendly sizes)

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 16 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 14th, 2026
Created on January 13th, 2012
Open Issues & Pull Requests: 19 (+0)
GitHub issues: Enabled
Number of forks: 266
Total Stargazers: 4,828 (+0)
Total Subscribers: 30 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 418.9 days
Mean response time: 1025.0 days
90th percentile: 3480.5 days
Tracked items: 22

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 19
Avg open age: 1,319 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 19
Comments in 7 days: 14
Events in 7 days: 32

Top labels

No label distribution available yet.

Most active issues this week

Detailed Description

go-humanize is a Go library that formats numbers and times into human-readable strings.

The library solves the problem of presenting raw numeric data in user-friendly formats. It provides functions to convert byte counts into readable sizes like "83 MB" or "79 MiB", express time differences in relative terms such as "12 seconds ago" or "3 days from now", format numbers with comma separators, generate ordinal suffixes for numbers, display values in SI notation, and handle English-specific formatting like pluralization and word series with conjunctions.

Developers should choose this library when building applications that display data to end users and need consistent, readable formatting across common data types. It suits any Go project requiring human-friendly output for file sizes, timestamps, or numeric values. The library is lightweight and focused on a narrow set of formatting tasks, making it suitable for inclusion in larger applications without adding substantial dependencies.

The project maintains a stable, minimal codebase with infrequent changes to core functionality. Updates are sparse and typically address specific issues rather than introducing new features. The development approach reflects a mature, maintenance-focused stance where the library's core functionality is considered complete and reliable.