jsonld-signatures - npm Package Versions

11.5.0 - 2024-12-17

Added

• Add support for signing @direction in documents when using the base LinkedDataSignature class. Other cryptosuites may already support @direction if they were not using this class.

11.4.0 - 2024-12-15

Added

• Add support for validating proof with domain expressed as an array.

11.3.2 - 2024-11-06

Fixed

• Ensure proof.@context is unmodified for JCS Data Integrity Cryptosuites.

11.3.1 - 2024-10-02

Fixed

• Ensure verification method ID is a string when checking controller proof purpose.

11.3.0 - 2024-08-01

Changed

• Use rdf-canonize directly to get latest updates and avoid reliance on jsonld package to provide it indirectly.

11.2.1 - 2023-05-14

Fixed

• Ensure internal _getProofs helper is synchronous.

11.2.0 - 2023-05-13

Added

• Add support for derive function to be implemented by the given cryptosuite. The derive function is used to derive a new document with a new proof based on an existing document (and proof). The derive function will be used when calling derive from jsonld-signatures. WARNING: The derive API will be considered unstable for a short while to ensure it meets the needs of external cryptosuites. It could change without a major version update (via a minor or patch release) until this notice is removed. If this is a concern for you, do not use it until this notice is removed.
• Any existing proofSet from the input document will be passed to the createProof and verifyProof functions in LinkedDataProof and LinkedDataSignature. It will also be passed to createVerifyData in LinkedDataSignature.

Changed

• Use @digitalbazaar/security-context to provide security contexts instead of the old security-context package.

11.1.0 - 2023-02-07

Added

• Allow custom canonizeOptions to be passed in the construction of a LD signature suites as a stop-gap until hard requirements for canonize options are either set or advised to be certain values by a W3C working group.

11.0.0 - 2022-08-23

Changed

• BREAKING: Use jsonld@8 to make use of safe mode. The safe mode is a more robust replacement for expansionMap.

Removed

• BREAKING: Remove expansionMap option. Now safe mode is used internally instead.

10.0.0 - 2022-06-06

Changed

• BREAKING: Update to jsonld@6.
  • Use of the packaged jsonld document loaders requires Node.js >=14.
• BREAKING: Update required Node.js to >=14.
  • Updated due to jsonld@6 requirements.
• Test on Node.js 18.x.
• Update eslint dependencies.
• Update development dependencies.