issues
search
digitalbazaar
/
data-integrity
Data Integrity Proof library for use with jsonld-signatures.
BSD 3-Clause "New" or "Revised" License
2
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Validate expires
#37
aljones15
closed
2 months ago
1
Add option to check validity period of proof (using `created` and `expires` and a current time param)
#36
dlongley
opened
2 months ago
0
Check previous proof
#35
aljones15
opened
2 months ago
1
Validate created
#34
aljones15
closed
2 months ago
2
library does not validate previousProof
#33
aljones15
opened
3 months ago
1
Default `date` to `null` in next major version
#32
dlongley
opened
3 months ago
0
Ensure `verificationMethod` is passed to `createVerifyData`.
#31
dlongley
closed
3 months ago
0
Add logic for verifying `proof.created`
#30
aljones15
closed
2 months ago
1
Improve default canonize options.
#29
dlongley
closed
4 months ago
1
Remove `created` from proof by passing `date:null` into DataIntegrityProof constructor.
#28
wes-smith
closed
9 months ago
2
Enable making `created` optional more explicitly
#27
dlongley
closed
9 months ago
1
Disallow adding v2 data integrity proofs to docs containing legacy / draft v1 data integrity proofs
#26
dlongley
opened
11 months ago
1
Disable coverage upload.
#25
davidlehn
closed
1 year ago
0
Fix badge.
#24
davidlehn
closed
1 year ago
0
Upload coverage report.
#23
davidlehn
closed
1 year ago
0
Add `legacyContext` flag to allow use of legacy context.
#22
JSAssassin
closed
1 year ago
0
Update context to v2.
#21
JSAssassin
closed
1 year ago
1
Refactor algorithm check to accommodate `requiredAlgorithm` represented as array.
#20
JSAssassin
closed
1 year ago
0
Support for jcs-based proofs according to specification
#19
rflechtner
opened
1 year ago
35
Add a "debugging cryptosuite" that can be plugged into a sign/verify process to debug it
#18
dlongley
opened
1 year ago
0
Add an example script that will sign and verify a document and provide debugging information
#17
dlongley
opened
1 year ago
0
Add `verifyProof` API
#16
dlongley
opened
1 year ago
0
Add `addProofChain` API
#15
dlongley
opened
1 year ago
0
Add `addProof` API
#14
dlongley
opened
1 year ago
0
Add v2 context support, default to v2 context, allow v1 for legacy use cases
#13
dlongley
closed
1 year ago
1
Make sure proof canonicalization is reproducible.
#12
rflechtner
closed
1 year ago
7
Add TS support?
#11
ntn-x2
opened
1 year ago
0
Add core data integrity functions for reuse in data integrity cryptosuites
#10
dlongley
opened
1 year ago
2
Consider renaming `algorithm` or change its expected values in cryptosuites
#9
dlongley
opened
1 year ago
0
Allow usage of VCDM 2.0 context as an alternative context.
#8
dlongley
closed
1 year ago
0
Ensure custom `createVerifyData` is called from `verifyProof`.
#7
dlongley
closed
1 year ago
0
Derive
#6
dlongley
closed
1 year ago
1
Add `matchProof()`
#5
JSAssassin
closed
1 year ago
0
Override `matchProof` in `DataIntegrityProof` to check `cryptosuite` value
#4
dlongley
closed
1 year ago
0
Allow passed cryptosuite to provide optional `createVerifyData` to replace default implementation
#3
dlongley
closed
1 year ago
0
Remove assertion method check.
#2
gannan08
closed
2 years ago
0
Initial
#1
gannan08
closed
2 years ago
0