Site profile
proto-runs.val.run
Built with react 19.1.0, react-dom 19.1.0, leaflet 1.9.4, leaflet-gpx 2.1.2, @atproto/api 0.15.5, @atproto/oauth-client-browser 0.3.15. 1 page and 14 stored files, last crawled 2026-10-03.
6 libraries 0 identifiers 7 third-party hosts 1 crawl open the site
Technologies and libraries
Recognised by fingerprinting the stored files and bundles against known releases; a version is the release the bytes match.
| Library | Version | Seen |
|---|---|---|
| react | 19.1.0 | 2026-10-03 |
| react-dom | 19.1.0 | 2026-10-03 |
| leaflet | 1.9.4 | 2026-10-03 |
| leaflet-gpx | 2.1.2 | 2026-10-03 |
| @atproto/api | 0.15.5 | 2026-10-03 |
| @atproto/oauth-client-browser | 0.3.15 | 2026-10-03 |
Tracking, tag and verification IDs
No analytics property, tag manager container, pixel or site-verification token was found in the stored source.
Third-party hosts
Hosts outside proto-runs.val.run that its pages load scripts, frames or stylesheets from, and that its own scripts name in absolute URLs (connect). Each links to every site loading from the same host.
| Host | Loaded as | Found in |
|---|---|---|
| bsky.social | connect | view source |
| cdnjs.cloudflare.com | script | view source |
| esm.sh | connect | view source |
| esm.town | script | view source |
| unpkg.com | script stylesheet | view source |
| www.osm.org | connect | view source |
| www.val.town | connect | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
One entry per crawl, newest first, with what changed since the crawl before: libraries, identifiers, third-party hosts and files. Historical versions stay viewable because the stored chunks are shared between versions, never copied.
-
first crawl
1 page, 14 files, 9.9 KB; 6 libraries, 0 identifiers, 7 third-party hosts
6 libraries added
- leaflet 1.9.4
- leaflet-gpx 2.1.2
- react 19.1.0
- react-dom 19.1.0
- @atproto/oauth-client-browser 0.3.15
- @atproto/api 0.15.5
8 third-party hosts added
14 files added
- https://proto-runs.val.run/ html
- https://proto-runs.val.run/frontend/index.tsx js
- https://proto-runs.val.run/frontend/components/App.tsx js
- https://proto-runs.val.run/shared/client_metadata.ts js
- https://proto-runs.val.run/frontend/context.ts js
- https://proto-runs.val.run/frontend/components/RunForm.tsx js
- https://proto-runs.val.run/frontend/components/SignIn.tsx js
- https://unpkg.com/[email protected]/dist/leaflet.js js
- https://cdnjs.cloudflare.com/ajax/libs/leaflet-gpx/2.1.2/gpx.min.js js
- https://esm.sh/[email protected]/jsx-runtime js
- https://esm.sh/[email protected]/client js
- https://esm.sh/@atproto/[email protected] js
- and 2 more
Questions about proto-runs.val.run
- How does PageSourceSearch know what proto-runs.val.run is built with?
- From the site's own source code. The crawler stores the exact bytes of its pages and first-party scripts; the libraries are recognised by fingerprinting that code against known releases, the identifiers are read out of the tag snippets, and the third-party hosts are the script, iframe and stylesheet sources in the HTML and the absolute URLs inside the scripts. Nothing is inferred from headers or guessed.
- How far back does the history of proto-runs.val.run go?
- To the first crawl the timeline lists. Every crawl records what the site looked like; when a file's content changes, its earlier version stays viewable because the stored chunks are never deleted, only mapped. A crawl that finds a file unchanged adds no copy.
- Can I see an older version of a script from proto-runs.val.run?
- Yes. In the stored files list, every date under a file opens the version that was live at that crawl, with the same viewer as the current one. The raw bytes can be downloaded from there.
- Which other websites use the same tracking IDs as proto-runs.val.run?
- Each identifier links to its reverse lookup, the list of every site in the index whose source carries the same id: the sites one analytics property or tag manager container is shared across.
Look up another site, browse sites by tracking ID, third-party host or technology. Site owners: see the crawler page for how stored pages are removed.