Skip to content

PostgreSQL plain credential checker

active 2023-08-152024-11-18 (UTC)

Complete coverage26,462 / 26,462 hourly files (100%) · 2 absent upstream2023-08-152026-08-21 (UTC)
Events
157
Pushes
24
Pull requests
5
Issues
32
Stars
28
Forks
2

Activity over time

Daily event counts in the loaded window

Line chart, 462 days from 2023-08-15 to 2024-11-18. Pushes: 24 total, peak 7 in a day. Pull requests: 5 total, peak 4 in a day. Issues: 32 total, peak 4 in a day. Comments: 43 total, peak 9 in a day. Stars: 28 total, peak 2 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
darold7024428
devrimgunduz9005
glushakov4003
Gabi2012654001
Furuncl3001
nikhil-postgres3002
did162000
rjuju2011
brunre012000
t-ushar1001
ragaoua1000
df7cb1001
hwlee-db1000
coroneltortuga1000

Recent activity

Latest issues, pull requests and releases

  • Issue#39darold2024-11-18 12:31
    how to map roleid from pg_banned_role to pg user
  • Pull request#40darold2024-11-18 12:31
  • Pull request#40darold2024-11-18 12:31
  • Issue comment#38darold2024-11-18 11:40
    server closed the connection unexpectedly when length of password is 24 chars
  • Issue#38darold2024-11-18 11:40
    server closed the connection unexpectedly when length of password is 24 chars
  • Issue comment#39darold2024-11-18 11:31
    how to map roleid from pg_banned_role to pg user
  • Issue comment#40darold2024-11-18 11:29
    Fix pg_banned_role.roleid value
  • Pull request#40darold2024-11-18 11:29
  • Issue comment#40rjuju2024-11-18 10:55
    Fix pg_banned_role.roleid value
  • Pull request#40rjuju2024-11-18 10:53
  • Issue comment#39darold2024-11-15 11:07
    how to map roleid from pg_banned_role to pg user
  • Issue#39Furuncl2024-11-15 09:55
    how to map roleid from pg_banned_role to pg user
  • Issue comment#38Furuncl2024-10-19 20:35
    server closed the connection unexpectedly when length of password is 24 chars
  • Issue comment#38darold2024-10-18 06:23
    server closed the connection unexpectedly when length of password is 24 chars
  • Issue#38Furuncl2024-10-17 12:49
    server closed the connection unexpectedly when length of password is 24 chars
  • Issue comment#35darold2024-08-03 07:49
    2.7 fails to build against PostgreSQL 17
  • Issue#35darold2024-08-03 07:49
    2.7 fails to build against PostgreSQL 17
  • Releasedarold2024-08-03 07:48
    Version 2.8
  • Issue comment#37darold2024-08-03 07:39
    Add a function for custom messages (ERROR: password length should match the configured credcheck.password_min_length)
  • Issue#37darold2024-08-03 07:39
    Add a function for custom messages (ERROR: password length should match the configured credcheck.password_min_length)
  • Issue comment#35devrimgunduz2024-07-30 12:50
    2.7 fails to build against PostgreSQL 17
  • Issue#34darold2024-07-19 04:11
    Special characters
  • Issue#37coroneltortuga2024-07-18 12:31
    Add a function for custom messages (ERROR: password length should match the configured credcheck.password_min_length)
  • Issue comment#35devrimgunduz2024-07-09 11:34
    2.7 fails to build against PostgreSQL 17
  • Issue comment#36t-ushar2024-06-10 05:24
    User ban is not happening after reaching the credcheck.max_auth_failure's value

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