Site profile
plasmic-supabase-demo.vercel.app
Built with @clerk/ui 1.34.0, @wix/design-system 1.328.0, @percy.ai/your-team 1.1.10. 1 page and 14 stored files, last crawled 2026-10-03.
3 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 |
|---|---|---|
| @clerk/ui | 1.34.0 | 2026-10-03 |
| @wix/design-system | 1.328.0 | 2026-10-03 |
| @percy.ai/your-team | 1.1.10 | 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 plasmic-supabase-demo.vercel.app 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 |
|---|---|---|
| analytics.plasmic.app | connect | view source |
| codegen.plasmic.app | connect | view source |
| docs.plasmic.app | connect | view source |
| pxmenvvvnubwxwkxszcq.supabase.co | connect | view source |
| reactjs.org | connect | view source |
| vercel.live | connect | view source |
| www.w3.org | 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, 1.3 MB; 3 libraries, 0 identifiers, 7 third-party hosts
3 libraries added
- @wix/design-system 1.328.0
- @percy.ai/your-team 1.1.10
- @clerk/ui 1.34.0
7 third-party hosts added
14 files added
- https://plasmic-supabase-demo.vercel.app/ html
- https://plasmic-supabase-demo.vercel.app/_next/static/chunks/0v42a~a7m0bw9.js js
- https://plasmic-supabase-demo.vercel.app/_next/static/chunks/10f6l8ihb1oiw.js js
- https://plasmic-supabase-demo.vercel.app/_next/static/chunks/178h450~099q0.js js
- https://plasmic-supabase-demo.vercel.app/_next/s…/turbopack-0e67f-7j_rcn..js js
- https://plasmic-supabase-demo.vercel.app/_next/static/chunks/0z9ukt~~2mawi.js js
- https://plasmic-supabase-demo.vercel.app/_next/static/chunks/0cslgeeyf2frc.js js
- https://plasmic-supabase-demo.vercel.app/_next/s…/turbopack-0expzl84.q5fr.js js
- https://plasmic-supabase-demo.vercel.app/_next/s…/_buildManifest.js js
- https://plasmic-supabase-demo.vercel.app/_next/s…BsgXt_DT9fhalze/_ssgManifest.js js
- https://plasmic-supabase-demo.vercel.app/_next/s…/_clientMiddlewareManifest.js js
- https://plasmic-supabase-demo.vercel.app/_next/static/chunks/16z1_8ghrc-gm.js js
- and 2 more
Questions about plasmic-supabase-demo.vercel.app
- How does PageSourceSearch know what plasmic-supabase-demo.vercel.app 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 plasmic-supabase-demo.vercel.app 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 plasmic-supabase-demo.vercel.app?
- 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 plasmic-supabase-demo.vercel.app?
- 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.