Skip to content

A package that reads your conventional commits and git history and recommends (or applies) a SemVer version bump for you

active 2023-09-192026-06-28 (UTC)

Complete coverage26,632 / 26,632 hourly files (100%) · 2 absent upstream2023-08-152026-08-28 (UTC)
Events
242
Pushes
71
Pull requests
33
Issues
14
Stars
1
Forks
4

Activity over time

Daily event counts in the loaded window

Line chart, 1014 days from 2023-09-19 to 2026-06-28. Pushes: 71 total, peak 7 in a day. Pull requests: 33 total, peak 4 in a day. Issues: 14 total, peak 2 in a day. Comments: 54 total, peak 7 in a day. Stars: 1 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
benduran147712432
wesleytodd11009
artemdanylenko11073
vladkampov5013
miguelramos5003
offirgolan4002
amybingzhao4002
brucespang1010

Recent activity

Latest issues, pull requests and releases

  • Pull request#35benduran2025-10-27 16:38
  • Pull request#34benduran2025-09-29 08:59
  • Issue#27benduran2025-09-23 12:13
    `git tag` step of applyRecommendedBumpsByPackage is not robust to git tag already existing
  • Issue comment#33vladkampov2025-04-07 15:37
    chore: add the new line indent when creating the packageJson file
  • Issue comment#33benduran2025-04-05 21:56
    chore: add the new line indent when creating the packageJson file
  • Pull request#33benduran2025-04-05 21:41
  • Issue comment#33vladkampov2025-03-19 18:36
    chore: add the new line indent when creating the packageJson file
  • Pull request#33vladkampov2025-03-14 11:30
  • Issue comment#31wesleytodd2025-01-08 13:37
    When passing `preid` repo transitive deps should lock not use ranges
  • Issue comment#30benduran2024-12-04 22:15
    Changes to package.json also change spacing
  • Issue comment#30offirgolan2024-12-04 21:27
    Changes to package.json also change spacing
  • Issue#30offirgolan2024-12-04 21:27
    Changes to package.json also change spacing
  • Issue comment#30benduran2024-12-02 21:16
    Changes to package.json also change spacing
  • Issue comment#30benduran2024-12-02 21:07
    Changes to package.json also change spacing
  • Issue comment#31benduran2024-11-29 19:43
    When passing `preid` repo transitive deps should lock not use ranges
  • Issue#31benduran2024-11-29 19:40
    When passing `preid` repo transitive deps should lock not use ranges
  • Pull request#32benduran2024-11-29 19:40
  • Issue comment#32benduran2024-11-26 20:53
    fix: use exact version instead of range operator when bumping prerelease or with a specific preid
  • Issue comment#32benduran2024-11-26 20:50
    fix: use exact version instead of range operator when bumping prerelease or with a specific preid
  • Issue comment#32benduran2024-11-26 20:48
    fix: use exact version instead of range operator when bumping prerelease or with a specific preid
  • Issue comment#32wesleytodd2024-11-26 17:05
    fix: use exact version instead of range operator when bumping prerelease or with a specific preid
  • Issue comment#31wesleytodd2024-11-22 22:52
    When passing `preid` repo transitive deps should lock not use ranges
  • Issue comment#31benduran2024-11-22 22:36
    When passing `preid` repo transitive deps should lock not use ranges
  • Pull request#32benduran2024-11-22 22:33
  • Issue comment#31wesleytodd2024-11-22 14:04
    When passing `preid` repo transitive deps should lock not use ranges

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.