Skip to content

digitalbazaar/data-integrity

View on GitHub ↗Related repositories →

Data Integrity Proof library for use with jsonld-signatures.

active 2023-10-292025-12-12 (UTC)

Partial coverage19,589 / 25,226 hourly files (78%) · 2 absent upstream · 5,634 failed, retryable2023-09-262026-08-12 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
55
Pushes
13
Pull requests
3
Issues
9
Stars
2
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 776 days from 2023-10-29 to 2025-12-12. Pushes: 13 total, peak 3 in a day. Pull requests: 3 total, peak 1 in a day. Issues: 9 total, peak 5 in a day. Comments: 19 total, peak 4 in a day. Stars: 2 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
dlongley19315
aljones158610
davidlehn6004
JSAssassin3210
wes-smith3200
silverpill3003
msporny2002
rflechtner2002
HelgeKrueger2002
codecov-commenter1001

Recent activity

Latest issues, pull requests and releases

  • Pull request#37dlongley2024-09-06 19:49
  • Issue comment#35codecov-commenter2024-09-04 21:32
    Check previous proof
  • Pull request#35aljones152024-09-04 21:25
  • Issue#33aljones152024-09-01 13:59
    library does not validate previousProof
  • Issue#32dlongley2024-08-30 19:02
    Default `date` to `null` in next major version
  • Issue comment#19msporny2024-06-09 16:18
    Support for jcs-based proofs according to specification
  • Issue comment#28davidlehn2024-02-13 02:35
    Remove `created` from proof by passing `date:null` into DataIntegrityProof constructor.
  • Issue comment#28davidlehn2024-02-13 02:35
    Remove `created` from proof by passing `date:null` into DataIntegrityProof constructor.
  • Issue#27dlongley2024-01-12 21:41
    Enable making `created` optional more explicitly
  • Issue comment#19rflechtner2023-12-21 10:49
    Support for jcs-based proofs according to specification
  • Issue comment#19HelgeKrueger2023-12-14 07:02
    Support for jcs-based proofs according to specification
  • Issue comment#19HelgeKrueger2023-12-13 08:48
    Support for jcs-based proofs according to specification
  • Issue comment#19silverpill2023-12-12 22:02
    Support for jcs-based proofs according to specification
  • Issue comment#26dlongley2023-12-12 01:02
    Disallow adding v2 data integrity proofs to docs containing legacy / draft v1 data integrity proofs
  • Issue#26dlongley2023-12-12 01:02
    Disallow adding v2 data integrity proofs to docs containing legacy / draft v1 data integrity proofs
  • Issue comment#19silverpill2023-12-12 00:03
    Support for jcs-based proofs according to specification
  • Issue comment#19dlongley2023-12-11 23:39
    Support for jcs-based proofs according to specification
  • Issue comment#19silverpill2023-12-08 21:38
    Support for jcs-based proofs according to specification
  • Issue comment#19msporny2023-12-08 14:40
    Support for jcs-based proofs according to specification
  • Issue comment#19rflechtner2023-12-08 13:31
    Support for jcs-based proofs according to specification
  • Pull request#22JSAssassin2023-11-11 17:21
  • Issue comment#21dlongley2023-11-10 17:29
    Update context to v2.
  • Issue#18dlongley2023-10-29 20:58
    Add a "debugging cryptosuite" that can be plugged into a sign/verify process to debug it
  • Issue#17dlongley2023-10-29 20:57
    Add an example script that will sign and verify a document and provide debugging information
  • Issue comment#10dlongley2023-10-29 20:55
    Add core data integrity functions for reuse in data integrity cryptosuites

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