Obfuscation Requirements

Obscuring KeyLines source code

KeyLines source code must be obscured within your application. To prevent it being accessed or reused by third parties you need to:

Exclude the words 'KeyLines' or 'Cambridge Intelligence' from any folder or path names.
Combine the KeyLines files with the source code from your application, so that KeyLines is not available as a separate file. We recommend using Terser with any of the following bundlers (any tool which achieves the results listed is acceptable):

Remove the copyright notice (this is usually a minification step).
Ensure you are not deploying source maps of your source code to your end users.
Fully integrate KeyLines into your product. We don't allow direct exposure of the KeyLines API to end users via your own API ‘wrapper’.

Before you deploy your code, you also need to check that:

The words 'KeyLines' or 'Cambridge Intelligence' aren’t in any folder or path names.
The final file containing KeyLines is at least 20% larger than the original KeyLines library file.
There are no Cambridge Intelligence copyright notices in your deployed code bundles.
You ensure compliance with the terms of any applicable Open Source Software ("OSS") licenses, which may include obligations such as replicating copyright notices or attribution requirements. For more details on OSS usage and licensing, please refer to the documentation provided with the relevant OSS.