github-traffic | Get the Github traffic for the specified repository | REST library
kandi X-RAY | github-traffic Summary
kandi X-RAY | github-traffic Summary
Get the last 14 days (this is Github's limitation) of Github traffic for the specified repository. The results will contain 4 keys (one for each of the traffic endpoints specified in the api documentation). See the example results for the expanded results from the example. See the other methods below to get results for a specific endpoint. Get referrers for the specified repository from the Github traffic api. Get paths for the specified repository from the Github traffic api. Get views for the specified repository from the Github traffic api. Get clones for the specified repository from the Github traffic api.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of github-traffic
github-traffic Key Features
github-traffic Examples and Code Snippets
Community Discussions
Trending Discussions on github-traffic
QUESTION
I created a repository last week with content for my website. It's a fork of quite known template. There is nothing interesting for anyone to see as of now, let alone to clone this repo. Nevertheless, there are already 12 unique cloners of the repo, as shown in Traffic section. Whats even more sus is that there is only one unique visitor to my repo (that's me from my second account), so none of the cloners even visited the repo, they just cloned it. Who are they? My hypothesis is:
- Someone backuping the internet, like archive.org (which shown no results when querying my repo's url)
- Malicious bots looking for leftover passwords or private keys
- Some error on the side of me or github
edit: This question might be related, but i feel like the cause might be different and I hope they would have already fixed the wrong script.
...ANSWER
Answered 2021-Feb-07 at 20:48GitHub provides a public events API where users can see almost every event that's happened publicly. This means that as soon as you create a repository and push data to it, anyone can notice that fact without ever looking at the page for your repository.
Without knowing who's cloning it, it's hard to say why it was cloned, but it could be people looking for credentials, researchers interested in popular languages or software development practices, or a wide variety of other things. Even GitHub probably doesn't know the answer, because all the information they would have on the cloners in such a case is the IP address and, if the user was authenticated, the username. As long as the repository is public and the level of usage is not excessive, this isn't something they'd think is intrinsically concerning and wouldn't inquire more deeply into.
I, too, wish I had some magical way to find this information out, because it is a curious phenomenon, but I'm not sure it's possible to know.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install github-traffic
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page