MapWeave source code must be obscured within your application. To prevent it being accessed or reused by third parties you need to:
- Exclude the words MapWeave or Cambridge Intelligence from any folder or path names.
- Combine all of the mapweave/**/*.js files with the source code from your application, so that MapWeave is not available as separate files. 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 MapWeave into your product. We don't allow direct exposure of the MapWeave API to end users via your own API ‘wrapper’.
Before deploying your code, check that:
- The words MapWeave or Cambridge Intelligence aren’t in any folder or path names.
- All of the final files containing one or more MapWeave.js files are at least 20% larger than the respective original.js files.
- 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.