JS Time Machine

The URL stayed the same. The code didn't.

Every time a browser on your site runs a script, it reports a fingerprint of the exact file. The JS Time Machine puts those fingerprints on a timeline, so you can see every version of a script your visitors loaded, when each one appeared, and when it went away.

What's at Stake

A list of script URLs can't tell you what those scripts were last Tuesday.

Third-party scripts change all the time, at the same address, with no notice. Most of those changes are harmless. One of them might not be. When something goes wrong, the first questions are always about time: what was running, since when, and for how long. A URL inventory has no answer to any of them, because the URL never changed.

Same Address

A new version looks exactly like the old one

A vendor ships an update, a CDN serves a different build, or an attacker swaps the file. In every case the script tag on your page is unchanged, so nothing that watches URLs will notice.

No Timeline

“When did this change?” has no answer

Without a record of each version and when it was seen, working out when a change happened means asking the vendor, digging through caches, or guessing.

Exposure Window

Incident response needs a start and an end

Whether you notify customers, and which ones, depends on how long a bad version was live. That window has to come from evidence, not an estimate.

What the JS Time Machine Does

The history of a script, from the browsers that ran it

Report URI already receives a cryptographic fingerprint of every script your visitors execute. The JS Time Machine searches those fingerprints by script and by time.

Version History

Every version, with when and how often it was seen

Search a script URL for an hour, a day, a month, or everything you keep. Each version is listed by its fingerprint, with when it was last seen, how many reports recorded it, and when it first appeared. A version we can identify shows its library name and release, so an unexpected one stands out straight away.

Learn more about CSP Integrity →
One Click In

From any script to its history

Every script on your CSP Integrity reports and in your Script Watch inventory links straight into the JS Time Machine, on the same period you were looking at, with that version highlighted. From any version, one more click shows the reports for it, and so which pages loaded it.

Learn more about Script Watch →
Versioned Paths

Follow a script even when its URL changes

Some scripts put their version in the path, so every release lives at a new address. End a search with * and the JS Time Machine covers every path that starts with it, listing each version alongside the paths it was served from. Query strings are ignored, so a cache-busting parameter never splits one script's history in two.

Learn more about JavaScript Integrity Monitoring →
Get Started

Start the timeline now. Before you need to look back.

One keyword on your policy. No code. History starts building from your first visitor.

30-day free trial  ·  No credit card  ·  One keyword  ·  No code

Questions It Answers

The questions that come up after a change

Each answer comes from what real browsers reported running on your pages, not from fetching the URL today.

Question Where the answer comes from
What changed, and when? The version live before a change, the one that replaced it, and when each was seen
Was this version on our site last month? Search the month and look for its fingerprint
How long was a bad version live? When the version first appeared and when it was last seen bracket the exposure
Which pages loaded it? Each version links to its CSP Integrity reports, with the page each one came from
Is everyone getting the same file? Several versions in the same hour point to a staged rollout, mixed CDN builds, or tampering aimed at some visitors
Architecture

One keyword. No code. Nothing in the path.

The JS Time Machine is built from CSP Integrity, a browser capability switched on by a keyword in your Content Security Policy. The browser reports a fingerprint for each script it runs. Your scripts are never routed through us, and nothing is added to your pages.

You don't need an existing CSP. A report-only header carrying just the keyword is enough to start.

Minimal setup — no existing CSP
Content-Security-Policy-Report-Only: script-src 'report-sha256';
  report-to default

Already running a policy? Add 'report-sha256' to your existing script-src. Either way you will need the Reporting-Endpoints and Report-To headers pointing at your Report URI endpoint — the exact headers are on your Setup page.

No code added to your pages

Built from what real browsers ran

Covers pages behind a login, including checkout

Third-party code from any origin your pages load

History as far back as your plan's retention

PCI DSS 6.4.3 & 11.6.1

Change detection you can show on a timeline

Requirement 11.6.1 asks you to detect unauthorised changes to the scripts on your payment pages, and 6.4.3 asks you to assure their integrity. Detecting a change is half of it. The other half is being able to show an assessor, for any script, which versions ran and when, and that each change was one you expected.

The JS Time Machine gives you that record from the browsers that loaded your payment pages. Script Watch raises the alert when something changes, and the wider evidence layer is set out on the PCI DSS Compliance page.

Scope

One layer in the stack. Here's how it fits.

The JS Time Machine shows the history of a script. Collecting the fingerprints, alerting on change and keeping the file itself are separate jobs handled alongside it.

The JS Time Machine does Pairs with
Lists every version of a script over time CSP Integrity for the fingerprints it is built from
Shows when a change happened Script Watch for the inventory and the alert
Identifies which version ran Script Vault for the file behind each fingerprint
Brackets an exposure window Threat Intelligence for flagging known-bad sources

Together, these form the client-side security visibility layer that sits between your CSP policy and your incident response process.