Filip Skokan 7ba492237a fix: allow any JSON numeric value for timestamp values ... > NumericDate > A JSON numeric value representing the number of seconds from > 1970-01-01T00:00:00Z UTC until the specified UTC date/time, > ignoring leap seconds. This is equivalent to the IEEE Std 1003.1, > 2013 Edition [POSIX.1] definition "Seconds Since the Epoch", in > which each day is accounted for by exactly 86400 seconds, other > than that non-integer values can be represented. See RFC 3339 > [RFC3339] for details regarding date/times in general and UTC in > particular.		2020-06-01 14:58:25 +02:00
..
help	feat: add opt-in objects to verify using embedded JWS Header public keys	2020-05-04 22:37:11 +02:00
jwa	refactor: aes_kw	2020-04-15 09:27:18 +02:00
jwe	perf: various codepaths refactored	2020-02-06 14:18:48 +01:00
jwk	feat: add opt-in objects to verify using embedded JWS Header public keys	2020-05-04 22:37:11 +02:00
jwks	feat: add opt-in objects to verify using embedded JWS Header public keys	2020-05-04 22:37:11 +02:00
jws	feat: add opt-in objects to verify using embedded JWS Header public keys	2020-05-04 22:37:11 +02:00
jwt	fix: allow any JSON numeric value for timestamp values	2020-06-01 14:58:25 +02:00
registry	refactor: allow ECDH-ES to be pluggable with extensions	2019-12-04 11:46:09 +01:00
errors.js	feat: add JWTExpired error and JWTClaimInvalid claim and reason props	2020-01-16 08:49:37 +01:00
index.js	feat: add JWT.sign/verify/decode	2019-02-27 22:38:30 +01:00