astralapp/astral

Organize Your GitHub Stars With Ease

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 19th, 2026
Created on March 14th, 2015
Open Issues & Pull Requests: 40 (+0)
GitHub issues: Enabled
Number of forks: 151
Total Stargazers: 3,581 (+0)
Total Subscribers: 23 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.5 hours
Mean response time: 45.5 days
90th percentile: 262.6 days
Tracked items: 9

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 859 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

  • bug 🐞 (2)
  • duplicate 👯‍♀️ (1)
  • enhancement ✨ (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Astral is a web application that helps you organize and manage your GitHub starred repositories with tags and collections.

The problem Astral solves is the difficulty of keeping starred repositories organized as collections grow. GitHub's native starring system provides no way to categorize or search through starred items, making it hard to rediscover useful projects later. Astral connects to your GitHub account via OAuth and lets you tag and organize your stars within its interface, creating a searchable, categorized view of your starred repositories.

You should choose Astral if you maintain a large number of GitHub stars and want to organize them by topic, language, or project type without relying on GitHub's built-in features. The project suits developers who want either a hosted solution or the ability to self-host their own instance. Self-hosting requires PHP, Node.js, and Yarn, along with setup of a GitHub OAuth application for authentication. A hosted version is available free of charge, removing the need for local deployment.

The project maintains a clear separation between its stable master branch and an active next branch representing future development. The maintainers request that contributors avoid submitting feature pull requests to master, as new features are being developed on next and may already be covered there. Bug fixes and security issue patches are still accepted on master. The project includes automated test workflows as part of its development process.