Skip to content

A collection of liteweight transparency logging tools, compatible with the Sigsum and Omniwitness ecosystems.

active 2023-09-112025-04-28 (UTC)

Complete coverage26,641 / 26,641 hourly files (100%) · 2 absent upstream2023-08-152026-08-29 (UTC)
Events
147
Pushes
55
Pull requests
6
Issues
34
Stars
9
Forks
4

Activity over time

Daily event counts in the loaded window

Line chart, 596 days from 2023-09-11 to 2025-04-28. Pushes: 55 total, peak 5 in a day. Pull requests: 6 total, peak 1 in a day. Issues: 34 total, peak 4 in a day. Comments: 26 total, peak 4 in a day. Stars: 9 total, peak 2 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
FiloSottile775527
rgdd330114
niels-moller8024
eliasrudberg4001
pgporada1010

Recent activity

Latest issues, pull requests and releases

  • Issue#28FiloSottile2025-03-12 11:05
    litewitness: support adding logs where the vkey name and origin are not the same
  • Issue#24FiloSottile2025-03-12 11:05
    litewitness: SIGSEGV: segmentation violation
  • Pull request#26FiloSottile2025-03-12 11:05
  • Issue#28eliasrudberg2025-03-10 08:47
    litewitness: support adding logs where the vkey name and origin are not the same
  • Pull request#26niels-moller2025-02-06 12:42
  • Issue#25FiloSottile2025-02-04 13:02
    sigsum-key and litewitess don't aggree on vkey format
  • Issue comment#24rgdd2025-01-30 08:09
    litewitness: SIGSEGV: segmentation violation
  • Issue comment#24eliasrudberg2025-01-27 15:11
    litewitness: SIGSEGV: segmentation violation
  • Issue#24rgdd2025-01-25 15:20
    litewitness: SIGSEGV: segmentation violation
  • Issue#23eliasrudberg2025-01-24 15:53
    litebastion: "HTTP/2 transport error" with type=recv_rststream_INTERNAL_ERROR
  • Issue comment#22rgdd2025-01-24 12:50
    litebastion and litewitness: need a way to disable logs exposed at /logz endpoint
  • Issue comment#22FiloSottile2025-01-24 10:44
    litebastion and litewitness: need a way to disable logs exposed at /logz endpoint
  • Issue#22eliasrudberg2025-01-24 10:31
    litebastion and litewitness: need a way to disable logs exposed at /logz endpoint
  • Issue#21rgdd2025-01-22 10:41
    Reject trailing arguments / missing params?
  • Issue comment#20niels-moller2025-01-16 06:46
    bastion: Close backend connections on failure
  • Issue comment#20FiloSottile2025-01-15 13:15
    bastion: Close backend connections on failure
  • Issue#10FiloSottile2025-01-15 13:07
    litebastion: Remove backends after SIGHUP?
  • Issue#15FiloSottile2025-01-15 12:34
    litebastion: Is too noisy by default (system logs are spammed)
  • Issue comment#20niels-moller2025-01-14 13:34
    bastion: Close backend connections on failure
  • Issue comment#20FiloSottile2025-01-14 11:41
    bastion: Close backend connections on failure
  • Issue#17FiloSottile2024-12-17 12:06
    witnessctl: Subcommand to remove a log
  • Issue#13FiloSottile2024-12-17 12:06
    NEWS file would be helpful
  • Pull request#20niels-moller2024-12-02 09:52
  • Issue#19rgdd2024-10-31 09:08
    litewitness: Document how to think about database backups
  • Issue#18rgdd2024-10-31 09:06
    litewitness: Document database schema

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