SDK versions
Every published verification.js build, with its integrity hash for pinning.
Every release of the embed SDK is published twice: at /v1/verification.js (the current
major, mutable) and at its exact version (immutable, safe to pin). Once a version is
published, its bytes at that path never change; the deploy refuses to overwrite it under
a different bundle.
Pin a version by naming it in place of v1 and adding the integrity attribute below,
which the browser checks before running the script:
1.1.0
September 13, 2026
<script src="https://sdk.dev.auvral.com/1.1.0/verification.js" integrity="sha384-waolEJKhnxlNKezDoNBiKf39++6MUoNkpDah/+UE/EK6gtP6qmE67YCKR9oNVRcZ" crossorigin="anonymous"></script>The widget copies the verification link to the clipboard from inside the frame, which a browser only permits when the embedding page delegates clipboard-write to it. The SDK sets that on the iframe it creates, so nothing changes in your embed: the same script tag and the same AuvralVerification.init() call. AuvralVerification.version reports 1.1.0.
1.0.0
September 12, 2026
<script src="https://sdk.dev.auvral.com/1.0.0/verification.js" integrity="sha384-Qrx50B1H41AaJ1/6dDlUcXbQHUMkmh8i8PYuNbIYBYqYCiESRUKb1zk0Dm3Q+PwA" crossorigin="anonymous"></script>First version published under the Stripe-style layout: /v1/verification.js (mutable within the major) and /1.0.0/verification.js (immutable, pinnable with SRI), both served from sdk.{stage}.auvral.com behind CloudFront. The root /verification.js is gone. AuvralVerification.version reports 1.0.0.
Next
- Web SDK: install and use the SDK.
- Browser requirements: CSP, Permissions-Policy, HTTPS.