anchor.diff:  
   It can be used for several purposes:
   
  -* You can serialize and sign or encrypt a user ID for unsubscribing of newsletters into URLs.
  -  This way you don't need to generate one-time tokens and store them in the database.
  +* You can serialize and sign or encrypt a user ID for unsubscribing of newsletters into
  +  URLs. This way you don't need to generate one-time tokens and store them in the
  +  database.
   * Same thing with any kind of activation link for accounts and similar things.
   * Signed or encrypted objects can be stored in cookies or other untrusted sources which
  -  means you don't need to have sessions stored on the server, which reduces the number of necessary
  -  database queries.
  -* Signed information can safely do a roundtrip between server and client in general which makes
  -  them useful for passing server-side state to a client and then back.
  +  means you don't need to have sessions stored on the server, which reduces the number
  +  of necessary database queries.
  +* Signed information can safely do a roundtrip between server and client in general which
  +  makes them useful for passing server-side state to a client and then back.
   * Safely send and receve signed or encrypted messages between components or microservices.
  -* Self contained token generation for use with completely stateless token based authentication.
  +* Self contained token generation for use with completely stateless token based
  +  authentication.
   
   
   == Project Maturity
  
positive.code: == Install
  
  This section covers the _buddy-sign_ library installing process and its requirements.
  
  === Requirements
  
  
negative.code: 
  === Claims validation
  
  _buddy-sign_ json web signature implements validation of a concrete subset of claims: *exp* (expiration
  time), *nbf* (not before), *iss* (issuer) and *aud* (audience).
  
  The validation is performed on decoding the token. If `:exp` claim is found and is posterior to
  