adobe-fonts/source-sans

Sans serif font family for user interface environments

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 18th, 2026
Created on August 9th, 2012
Open Issues & Pull Requests: 42 (+0)
GitHub issues: Enabled
Number of forks: 243
Total Stargazers: 3,745 (+0)
Total Subscribers: 131 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.5 days
Mean response time: 30.2 days
90th percentile: 123.3 days
Tracked items: 13

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 745 days
Stale 30+ days: 8
Stale 90+ days: 7

Recent activity

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

Top labels

  • enhancement (5)
  • not a font bug (2)
  • addressed in source files (1)
  • bug (1)
  • fixed (1)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Source Sans is a sans serif font family designed for user interface environments.

The project addresses the need for typefaces optimized specifically for UI contexts rather than print or general-purpose use. Source Sans is built as a set of OpenType fonts and includes support for variable fonts, allowing designers and developers to access a range of weights and styles from a single font file. The fonts are distributed as both OTF and TTF formats, giving flexibility in deployment across different platforms and applications.

Teams building user interfaces should consider Source Sans when they need a professional, open-source typeface that has been intentionally engineered for screen rendering and UI legibility. The project suits organizations that want to avoid licensing restrictions and maintain control over their typography stack. The source files and build instructions are available in the repository, enabling customization for teams with specific typographic needs.

The project maintains an open contribution model, with a clear path for users to report issues or suggest improvements directly to the designer. Development activity centers on managing releases and responding to community feedback through the issue tracker.