loading...

GitHub Traffic Viewer

mokkapps profile image Michael Hoffmann ・1 min read

I have built a website to be able to check all GitHub repo traffic views of an account:

https://github-traffic-viewer.netlify.com/

Source code is available at GitHub.

My motivation (taken from my GitHub traffic CLI blog post):

Since I published my first projects on GitHub I really enjoyed viewing the traffic on my repositories. It is really interesting to see how many people visit or clone my repositories.

Unfortunately it costs a lot of time to click through all available repositories and I was looking for a more elegant way.

Used technologies: Gatsby.js, Netlify, Firebase, React.js

GitHub Traffic Viewer

Let me know what you think about it and if it is also helpful for you!

Discussion

pic
Editor guide
Collapse
ben profile image
Ben Halpern

Tried it out. Pretty neat 🙂

Collapse
ruchinmunjal profile image
ruchinmunjal

Can the same be done for bitbucket?

I recently interviewed for a job and shared a private repo for the interviewer. I want to know if they even visited :P

Collapse
mokkapps profile image
Michael Hoffmann Author

Mhm, I don't think so. I just took a quick look at the Bitbucket REST API but could not find a similar endpoint to fetch the views of a repository.

Alternatively, according to this blog post from 2012 you could also track your repo via Google Analytics.

Collapse
ruchinmunjal profile image
ruchinmunjal

Thank you so much Michael, for taking a look at the API. If I'm not wrong, the analytics would only be able to pick future views and not past? Since in my case I had given the repo link almost a week ago. Anyway, I got good news yesterday, I've been selected. :)

Thread Thread
mokkapps profile image
Michael Hoffmann Author

Yes, the analytics data would only represent future views. Nevertheless, congratulations for beeing selected ;-)

Collapse
bbasile profile image
Basile B.

does not work w/ third party cookies disabled.

Collapse
mokkapps profile image
Michael Hoffmann Author

Yes, unfortunately third party cookies are needed to be able to authenticate at GitHub via Firebase