Open Source
Report Card
Powered by Fusion

Tom Clancy is an awesome JavaScripter who loves pushing code. Tom is a fulltime hacker who works best in the afternoon (around 3 pm).

Tom's developer personality is very similar to blob8108's but blob8108 is more of a pusher. There is also an uncanny similarity between Tom's activity stream and those of Hsiaoming Yang, Wichert Akkerman, Piotr Zalewa, and Jason Grout.

It seems like Tom is—or should be—friends with Jonathan Barratt. With this in mind, it's worth noting that Jonathan is more of a follower. There is also an obvious connection between Tom and Omer Katz, yflau, Daniel Lindsley, and Saul Shanabrook.

These days, Tom is most actively contributing to the repositories: xHFT/pencilme-dev, tclancy/configurations, pybee/duvet, tclancy/django-helpdesk, and rennat/pynliner.


The two following graphs show Tom Clancy's average weekly and daily schedules. These charts give significant insight into Tom's character as a developer. The colors in the charts indicate the fraction of events that are pushes, issue comments, new issues, pull requests, and forking.

Note: an attempt has been made to show these plots in in the correct timezone (based on Tom's location listed on their GitHub profile) but this procedure is imperfect at best.

We already know that Tom loves pushing code but the following chart sheds some light onto what Tom does with their open source time. In the full event stream analyzed for this report, there are a total of 240 events recorded for Tom. The colors in the pie chart below indicate the number of events that are pushes, issue comments, new issues, pull requests, and forking.

Tom has contributed to repositories in 6 languages. In particular, Tom seems to be a pretty serious JavaScript expert with a surprisingly broad knowledge of Python as well. The following chart shows the number of contributions Tom made to repositories mainly written in JavaScript, Python, Objective-C, Ruby, and Shell.

Note: like stats? Of course you do. Did you know that you can get access to the raw data that was used to generate this page in JSON format?

Is this page about you? You don't like the things that it's saying? I'm very sorry about that! Remember that it is just meant to be a toy and not meant to be taken seriously but if you must, you're welcome to opt-out at any time.

Want to try another user? Enter a GitHub username