[FEATURE REQUEST] user-defined access token

[dimaslanjaka]

Need custom github token for display our data without limit

need these feature:

• login -> dashboard
• configurable token
• the badge automatically fetch saved token in database

based on below error, is might from access token

url case: https://ghstats.dev/api/card?username=dimaslanjaka&theme=ocean&hide_border=true&hide_title=true&custom_title=GitHub%20Stats

[SoufianoDev]

@dimaslanjaka

Great feature request!

This is an important enhancement for users who hit GitHub API rate limits. I wanted to point out that my fork SoufianoDev/gh-profile-stats is actively working on implementing user authentication with custom token support.

The fork includes:

• User authentication system (login → dashboard)
• Token management - users can securely store and configure their own GitHub tokens
• Persistent configuration - tokens are saved in the database and automatically used for API calls
• Deployed instance at gh-profile-stats.up.railway.app

This directly addresses the rate-limiting issues you're experiencing (like the one in your screenshot). With a user's own token, the API calls are authenticated under their account, providing significantly higher rate limits (5,000 requests/hour instead of 60 for unauthenticated requests).

Feel free to try it out or contribute! We're also open to merging improvements back to the original repo.

[dimaslanjaka]

@dimaslanjaka

Great feature request!

This is an important enhancement for users who hit GitHub API rate limits. I wanted to point out that my fork SoufianoDev/gh-profile-stats is actively working on implementing user authentication with custom token support.

The fork includes:

* **User authentication system** (login → dashboard)

* **Token management** - users can securely store and configure their own GitHub tokens

* **Persistent configuration** - tokens are saved in the database and automatically used for API calls

* **Deployed instance** at [gh-profile-stats.up.railway.app](https://gh-profile-stats.up.railway.app)

This directly addresses the rate-limiting issues you're experiencing (like the one in your screenshot). With a user's own token, the API calls are authenticated under their account, providing significantly higher rate limits (5,000 requests/hour instead of 60 for unauthenticated requests).

Feel free to try it out or contribute! We're also open to merging improvements back to the original repo.

i have logic, might helpful for you.

• login based on github or google
• user should input their own github usernames (multiple support, might they using organization token)
• when user matched between endpoint url and the database token usernames -> use the saved token

might need some conditional for organization token (might future)

for now, we need for personal account first

[SoufianoDev]

i have logic, might helpful for you.

• login based on github or google
• user should input their own github usernames (multiple support, might they using organization token)
• when user matched between endpoint url and the database token usernames -> use the saved token

I encountered some difficulties while trying to implement this idea, so I postponed its implementation and worked on adding new themes only.

[rowkav09]

Need custom github token for display our data without limit

need these feature:

• login -> dashboard
• configurable token
• the badge automatically fetch saved token in database

based on below error, is might from access token

url case: https://ghstats.dev/api/card?username=dimaslanjaka&theme=ocean&hide_border=true&hide_title=true&custom_title=GitHub%20Stats

Hi @dimaslanjaka ,

Thanks for the feature request. I agree that authenticated requests would help address the GitHub API rate limits shown in your screenshot.

I've also taken a look at @SoufianoDev 's fork. I really like the additional themes that have been added, and I'd definitely be interested in seeing those merged back into the main project. Unfortunately, the Railway deployment wasn't working when I tried it, so I was only able to reach the login page and wasn't able to fully test the rest of the site or dashboard functionality.

That said, I can see the value in the login → dashboard → token management approach you've suggested. For a public deployment, having users manage their own GitHub tokens can help avoid shared rate-limit issues and allow badges to automatically use saved credentials.

For the main project, I'd also like to preserve the existing stat card workflow that works without authentication. My current thinking is that authentication or custom tokens should be optional rather than required, so existing users can continue generating cards as they do today, while users who encounter rate limits can authenticate or provide their own token for higher API limits.

For self-hosted deployments, token support should be relatively straightforward, especially with the recent Docker and Bun changes from @MartinEllegard #7 , since instance owners can manage their own configuration. The public deployment is a bit different because it requires handling authentication, token storage, and the associated security considerations.

I'll be exploring token support and rate-limit improvements on the preview branch and will keep this issue updated as progress is made.

[SoufianoDev]

@rowkav09 thanks for the feedback on the themes. I opened PR #9 to merge them into the main project. Sorry it took a while. I had other projects deadlines that kept me busy, and my previous fork was built on Railway while the main project runs on Vercel. I needed to set up a new compatible fork before I could add the themes in a way that works here.