cheggaaa/pb

Console progress bar for Golang

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 18th, 2026
Created on December 4th, 2012
Open Issues & Pull Requests: 25 (+0)
GitHub issues: Enabled
Number of forks: 274
Total Stargazers: 3,725 (+0)
Total Subscribers: 35 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 61.0 days
Mean response time: 45.3 days
90th percentile: 73.1 days
Tracked items: 3

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 2,026 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

pb is a console progress bar library for Go.

The library solves the problem of displaying progress feedback in terminal applications. It provides a straightforward way to render progress bars in the console, allowing developers to show users the status of long-running operations. The tool uses Go's built-in text/template package for rendering, enabling both predefined progress bar styles and custom templates tailored to specific needs.

Developers should choose this library when building command-line tools that perform operations where users benefit from visual progress feedback. It is particularly suited for IO operations and batch processing tasks. The library supports customizable templates, allowing developers to define the appearance of progress bars using template syntax and compose them from available elements like fill characters, borders, and status indicators. Unicode progress bar glyphs can be enabled via environment variable for terminals with appropriate font support.

The project maintains active development with regular updates and bug fixes. The codebase shows consistent attention to both core functionality and user-facing improvements. Documentation is kept current alongside the code, with separate guidance provided for different major versions to help users understand migration paths and version-specific features.