defunkt/gist

Potentially the best command line gister.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 52 minutes ago
Added to GitGenius on September 18th, 2026
Created on October 10th, 2008
Open Issues & Pull Requests: 55 (+0)
GitHub issues: Enabled
Number of forks: 346
Total Stargazers: 3,807 (+0)
Total Subscribers: 58 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 43.3 days
Mean response time: 236.3 days
90th percentile: 814.3 days
Tracked items: 20

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

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

gist is a command-line tool for creating and managing Gist snippets directly from the terminal.

The tool solves the problem of sharing code snippets without leaving your editor or command line. It allows developers to quickly create Gists from files or standard input and copy the resulting URL to the clipboard, streamlining the workflow of sharing code with others. The approach is straightforward: pipe content to the tool or specify files as arguments, and it handles authentication and posting to the Gist service.

The tool suits developers who frequently share code snippets and prefer working within terminal environments. It is particularly valuable for those already embedded in command-line workflows who want to avoid context-switching to a web browser. Anyone considering adoption should be aware that the tool integrates with the Gist service and requires appropriate authentication setup to function.

The project shows sparse recent development activity, with infrequent commits and minimal ongoing maintenance. Issues and pull requests receive slow response times, indicating limited active engagement from maintainers. The codebase remains relatively stable despite the low activity level, suggesting the tool is in a maintenance-only state rather than undergoing active feature development.