Skip to content

A chrome plugin enabling you to track when your mails are read by your recipient.As soon as your recipient opens the mail you are notified that your mail is read by recipient.

active 2025-05-232025-06-08 (UTC)

Partial coverage12,712 / 14,504 hourly files (88%) · 2 absent upstream · 1,786 failed, retryable2024-12-142026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
65
Pushes
16
Pull requests
4
Issues
0
Stars
0
Forks
9

Activity over time

Daily event counts in the loaded window

Line chart, 17 days from 2025-05-23 to 2025-06-08. Pushes: 16 total, peak 16 in a day. Pull requests: 4 total, peak 4 in a day. Issues: 0 total, peak 0 in a day. Comments: 33 total, peak 33 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

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

ContributorContributionsPushesPRsComments
gapcomputer231616
Merango4004
Vuk79124013
Hattrix34004
Aflame71214013
Ralfmal3003
CryptoSCK3003
Santix12343003
Alexdyn19272002
KOIIFLONG2011
jmz19841001

Recent activity

Latest issues, pull requests and releases

  • Issue comment#3CryptoSCK2025-05-23 05:51
    Configure Babel Transpilation and Jest Testing for MailGeek Chrome Extension
  • Issue comment#4gapcomputer2025-05-23 05:50
    Configure Babel and Jest for ES6 Compatibility in Chrome Extension
  • Issue comment#4Vuk79122025-05-23 05:50
    Configure Babel and Jest for ES6 Compatibility in Chrome Extension
  • Issue comment#3gapcomputer2025-05-23 05:48
    Configure Babel Transpilation and Jest Testing for MailGeek Chrome Extension
  • Issue comment#4KOIIFLONG2025-05-23 05:48
    Configure Babel and Jest for ES6 Compatibility in Chrome Extension
  • Issue comment#4Hattrix32025-05-23 05:48
    Configure Babel and Jest for ES6 Compatibility in Chrome Extension
  • Issue comment#3Vuk79122025-05-23 05:48
    Configure Babel Transpilation and Jest Testing for MailGeek Chrome Extension
  • Issue comment#3Ralfmal2025-05-23 05:48
    Configure Babel Transpilation and Jest Testing for MailGeek Chrome Extension
  • Issue comment#3Aflame71212025-05-23 05:48
    Configure Babel Transpilation and Jest Testing for MailGeek Chrome Extension
  • Issue comment#4Merango2025-05-23 05:47
    Configure Babel and Jest for ES6 Compatibility in Chrome Extension
  • Issue comment#4Santix12342025-05-23 05:47
    Configure Babel and Jest for ES6 Compatibility in Chrome Extension
  • Issue comment#4gapcomputer2025-05-23 05:47
    Configure Babel and Jest for ES6 Compatibility in Chrome Extension
  • Issue comment#3Hattrix32025-05-23 05:47
    Configure Babel Transpilation and Jest Testing for MailGeek Chrome Extension
  • Issue comment#3Santix12342025-05-23 05:47
    Configure Babel Transpilation and Jest Testing for MailGeek Chrome Extension
  • Issue comment#3Merango2025-05-23 05:47
    Configure Babel Transpilation and Jest Testing for MailGeek Chrome Extension
  • Issue comment#3gapcomputer2025-05-23 05:47
    Configure Babel Transpilation and Jest Testing for MailGeek Chrome Extension
  • Issue comment#1CryptoSCK2025-05-23 05:42
    Configure Babel, ES6, and Testing Infrastructure for MailGeek Chrome Extension
  • Pull request#4Aflame71212025-05-23 05:37
  • Issue comment#2CryptoSCK2025-05-23 05:37
    Configure Babel and Jest for MailGeek Chrome Extension Testing
  • Pull request#3KOIIFLONG2025-05-23 05:35
  • Issue comment#2Ralfmal2025-05-23 05:34
    Configure Babel and Jest for MailGeek Chrome Extension Testing
  • Issue comment#2Alexdyn19272025-05-23 05:34
    Configure Babel and Jest for MailGeek Chrome Extension Testing
  • Issue comment#2Hattrix32025-05-23 05:34
    Configure Babel and Jest for MailGeek Chrome Extension Testing
  • Issue comment#2Merango2025-05-23 05:33
    Configure Babel and Jest for MailGeek Chrome Extension Testing
  • Issue comment#2gapcomputer2025-05-23 05:33
    Configure Babel and Jest for MailGeek Chrome Extension Testing

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