resume/resume.github.com
Resumes generated using the GitHub informations
62.9k stars · 1.4k forks · JavaScript
Avoid
Avoid: no human commits in a year, and most questions go unanswered.
Why
- No human commits since August 2016, and only 0 of 7 recent issues got a maintainer reply. (source 1, source 2, source 3, source 4)
- GitHub found no license file, so the code is not clearly licensed for reuse. (source 1)
What would change this
- A release or merged commit from a maintainer, or replies to recent issues.
- A license file is added.
Maintenance
CompleteDormant
- Human commits, 30 days
- 0
- Human commits, 90 days
- 0
- Human commits, 365 days
- 0
- Bot share of commits, 365 days
- 0%
- Last commit
- Aug 5, 2016 (10 years ago)
- Last human commit
- Aug 5, 2016 (10 years ago)
- Authors, 90 days
- 0
- Last release
- none found
- Median PR merge time
- 4 hours
Responsiveness: of 7 recent issues, 0% got a maintainer reply. Median first response: n/a.
- No human commits in 365 days, and most issues go unanswered.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Organization
- Commits sampled
- 100 since Nov 19, 2013
- Authors for half of commits
- 2
- Authors for 80% of commits
- 10
- Contributors
- 46
Top committers
- u2: 31% of commits
- David Coallier: 23% of commits
- Joah Gerstenberg: 7% of commits
- PeterDaveHello: 6% of commits
- shakeelmohamed: 3% of commits
- No human commits in the last 365 days, so shares use the newest 100 commits back to 2013-11-19T17:25:54Z.
Sources: Commits, Contributors
Stars
CompleteMostly organic, confidence high
Bursts
- Nov 18, 2013 to Dec 20, 2013: about 5.9k more stars than usual, peak 593 in one day, a spike that tapers off. No outside explanation found, so this burst is unexplained.
- Mar 20, 2014 to Mar 21, 2014: about 57 more stars than usual, peak 59 in one day, a spike that tapers off. We couldn't check for an outside explanation.
- May 3, 2014 to May 9, 2014: about 1k more stars than usual, peak 395 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- May 12, 2014 to May 14, 2014: about 163 more stars than usual, peak 90 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Apr 29, 2015 to Apr 30, 2015: about 77 more stars than usual, peak 73 in one day, a spike that tapers off. We couldn't check for an outside explanation.
- Apr 8, 2017 to Apr 18, 2017: about 527 more stars than usual, peak 130 in one day, a shape we can't classify. Outside explanation: a jump in forks.
- Jul 23, 2017 to Aug 4, 2017: about 942 more stars than usual, peak 280 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Aug 18, 2018 to Aug 20, 2018: about 117 more stars than usual, peak 80 in one day, a spike that tapers off. No outside explanation found, so this burst is unexplained.
- Feb 4, 2019 to Feb 6, 2019: about 106 more stars than usual, peak 70 in one day, a spike that tapers off. No outside explanation found, so this burst is unexplained.
- Sep 24, 2019 to Sep 26, 2019: about 95 more stars than usual, peak 69 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jul 10, 2020 to Jul 11, 2020: about 65 more stars than usual, peak 42 in one day, a shape we can't classify. Outside explanation: a jump in forks.
- Aug 20, 2020 to Aug 25, 2020: about 318 more stars than usual, peak 147 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Oct 5, 2020 to Oct 8, 2020: about 82 more stars than usual, peak 36 in one day, a flat block of stars. We couldn't check for an outside explanation.
- Dec 10, 2020 to Dec 16, 2020: about 264 more stars than usual, peak 109 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Oct 4, 2021 to Oct 6, 2021: about 99 more stars than usual, peak 59 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Nov 14, 2021 to Nov 16, 2021: about 59 more stars than usual, peak 36 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Feb 9, 2022 to Feb 13, 2022: about 64 more stars than usual, peak 26 in one day, a spike that tapers off. We couldn't check for an outside explanation.
- May 6, 2022 to May 27, 2022: about 5.6k more stars than usual, peak 2.4k in one day, a spike that tapers off. Outside explanation: a Hacker News post, a jump in forks, a jump in issues and pull requests.
- Jun 24, 2023 to Jun 24, 2023: about 60 more stars than usual, peak 68 in one day, a spike that tapers off. We couldn't check for an outside explanation.
- 108 stars on a repo created before February 2013 have no date, so they aren't in the chart.
- Engagement is low for a repo this size (forks, watchers, issues, contributors).
- 2 stars GitHub has since removed (tracked since Oct 13, 2026).
Anyone can buy stars for any repo; bursts alone don't prove the owner did.
- Some star bursts have no matching forks, issues, releases, or launch coverage.
- Forks, watchers, issues, and contributors are low for the number of stars.
- Anyone can buy stars for any repo, so this describes the star history only.
- 108 stars on the creation day are undated (before 2013-02-10) and are not counted.
Sources: How star history is analyzed
Risk
CompleteFlags
- Warning: GitHub finds no license for this repository, so default copyright rules apply and no reuse is granted. Details
- Info: The OpenSSF Scorecard for this project is 2.2 out of 10 (deps.dev). Details
License
- Now
- No license found
- A year ago
- Not known
Packages
No published packages found.
OpenSSF Scorecard: 2.2 out of 10 (via deps.dev).
Sources: GitHub: resume/resume.github.com
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/resume/resume.github.com)Earlier verdicts
- Oct 14, 2026: Avoid
- Oct 13, 2026: Avoid
- Oct 13, 2026: Avoid
Computed 17 hours ago · method 2026.10.2