Documentation

Guides for protecting production JavaScript

Reference guides for release workflows, command-line usage, cross-file protections, and the desktop app.

Build And Release Workflows Download Desktop
Inside The Docs

Practical guides, not placeholder pages.

How-to guides Start with release sequencing and command-line usage, then move into feature-specific references.
Advanced protection Browse cross-file controls like Replace Globals and Protect Members when a build spans multiple scripts.

Live status check

  • /v1/health.ashx
  • 10 seconds
  • Your browser only — results are not sent anywhere else

A small in-page status widget. Hitting this page starts a 10-second-interval poll of the JSO health endpoint and shows the result. Useful when you want a glance at "is JSO up right now" without leaving the docs.

Checking…
Endpoint
/v1/health.ashx
Last check
—
Round-trip time
—
Reported version
—
Reported uptime
—

All metrics here come from in-browser observation. JSO doesn't see this page's polling traffic differently from any other client of /v1/health.ashx.

Recent checks

Last 20 results. Cleared on page reload.

When Status HTTP RTT
No checks yet — the first one runs in a moment.

If the widget says FAIL but the site loaded

That usually means the load balancer / CDN / WAF in front of JSO is serving the marketing site fine but rejecting /v1/health.ashx for some unrelated reason — a firewall rule, a bot-detection challenge, or a CORS-stripping proxy. Sustained FAIL while the rest of the site works is a routing issue, not a JSO outage. See the health endpoint runbook for the same observation in prose.

Wiring this into your own dashboard

Everything this page does, your monitoring tool can do without us:

curl -fsS https://www.javascriptobfuscator.com/v1/health.ashx \
    | jq -e '.ok == true and .uptimeSeconds > 0'

The health-endpoint doc has Pingdom / BetterStack / UptimeRobot / Datadog Synthetics templates.