The version of the library we wrapped (
http://code.google.com/p/crypto-js/) at the time was not the latest. (The successor to that library is
https://github.com/digitalbazaar/forge.) This was due to it being relatively easy to convert over to a Servoy scope. We tried to to the latest version but:
1. Servoy doesn't support any of the JS modules implementations. Since most libraries are composed of modules, you end up having to mash everything together in one file to then put in a scope.
2. Most libraries nowadays are using a version of JS that Servoy doesn't support.
I actually messed around last year with Babel to transpile modern JS code into an output that Servoy might recognize thinking to solve both of the above challenges. And interesting experiment but you still have to convert that output into Servoy scopes format.
Summary: when you reach this edge of Servoy's capabilities it's likely better to drop into Java. Another intriguing option with Servoy 8 is use its websockets implementation to send chores over to other servers and get responses back quickly (can also just use REST or exec).