ScriptX License Verification

ScriptX License Verification is a small SvelteKit application that validates a MeadCo ScriptX license for use on a domain. It connects to ScriptX Services for Windows PC running locally to verify if the license is valid, expired, or not found, and provides appropriate messages based on the verification results. If the license is valid key license details can be displayed.

Use

• Download the file 'app-vX.X.X.zip' from this repo and extract it to a folder named 'verify' at the root (/verify) on your server.
• On a PC on which ScriptX.Services for Windows PC is installed, open the '/verify/index.html' file in a web browser to run the application.
• Enter the license guid and the url to the license file (typically lic.mlf) (or "warehouse" can be used) in the input fields and click the "Verify" button to check the license status.
• The application will display the verification result, including the license status (valid, expired, or not found) and the enabled options and domains associated with the license.
• Click the "print" button to print the verification result with the installed version of ScriptX.Services for Windows PC.

Example

The evaluation license can be verified here:

https://support.meadroid.com/verify/

Use the evaluation license GUID. This can be found here:

https://support.meadroid.com/deploy/services/

Features

• Connects to MeadCo.ScriptX.Print service on http://127.0.0.1:41191
• Uses the MeadCoScriptXJS and ScriptX.Print.Client libraries to communicate with the local service (see app.html)
• Verifies a license GUID against a supplied URL or warehouse / securewarehouse
• Shows:
  • License revision
  • Valid from / until dates
  • Licensed company
• Simple details page for printing or inspecting the full license
• Build output packaged as a versioned zip (app-vX.Y.Z.zip)

Development

Requirements

• Node.js (LTS recommended)
• npm
• ScriptX Services for Windows PC running on the local machine

Install dependencies:

npm install

Run the development server:

npm run dev

SvelteKit will report the local URL (typically http://localhost:5173).

Build

Create a production build:

npm run build

This will:

1. Run vite build and prerender the app into the build folder.
2. Create a zip archive app-v<package-version>.zip in the project root containing the contents of build.

You can deploy the contents of the build folder (or the zip) to any static host.

Notes on security advisories

This project is built with SvelteKit and deployed as a static site using @sveltejs/adapter-static. Some npm audit reports may reference low‑severity issues in transitive server-side dependencies (such as cookie) that are only used during development/build time. No SvelteKit server runtime is deployed with this app.

Customisation

To install the application in an alternative folder edit the svelte.config.js file and change the base path to the new folder. Also edit the function goBack() in the src/routes/print/+page.svelte file to point to the new folder. The default is /verify.