wesbos/awesome-uses

A list of /uses pages detailing developer setups, gear, software and configs.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 5 minutes ago
Added to GitGenius on September 12th, 2026
Created on June 12th, 2017
Open Issues & Pull Requests: 26 (+1)
GitHub issues: Enabled
Number of forks: 1,546
Total Stargazers: 5,299 (+0)
Total Subscribers: 53 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 163.7 days
Mean response time: 291.0 days
90th percentile: 696.9 days
Tracked items: 6

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: 0
Avg open age: 401 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

Awesome Uses is a curated list aggregating developer setup pages that document tools, hardware, software, and configurations.

The project solves the problem of discovering what tools and setups other developers use by collecting and organizing `/uses` pages from across the web. Rather than searching individually for how specific developers configure their environments, the tool centralizes these setups in one browsable location. The approach works by maintaining a structured data file where contributors add links to individual developer `/uses` pages, which are then rendered into a searchable directory accessible through the associated website.

Developers should choose this if they want to explore how peers in the industry configure their workspaces, find recommendations for tools and hardware, or share their own setup with the community. It suits anyone looking for inspiration on development environments, from those building their first setup to experienced developers seeking new tools. The project is particularly valuable for discovering lesser-known tools and seeing real-world configurations rather than marketing materials.

The project maintains an active contribution model where community members submit new `/uses` pages through pull requests to the data file, with a dedicated contribution guide provided to ensure consistency. The README is automatically generated from the underlying data structure, preventing manual maintenance overhead and keeping documentation synchronized with the actual content list.