Skip to content

As far as the API's contract and behaviour are concerned, it should behave exactly like AWS SES. But it should not actually send any mail out, rather it should keep statistics of the API usage and make this available for analysis (as it will be used in testing)

active 2025-01-112025-01-11 (UTC)

Complete coverage26,504 / 26,504 hourly files (100%) · 2 absent upstream2023-08-152026-08-23 (UTC)
Events
4
Pushes
2
Pull requests
0
Issues
0
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 1 days from 2025-01-11 to 2025-01-11. Pushes: 2 total, peak 2 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 0 total, peak 0 in a day. Comments: 0 total, peak 0 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
Ankit3892200

Recent activity

Latest issues, pull requests and releases

No issue or PR events — this repo's activity is pushes only.

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.