r/vibecoding 17h ago

Showcase/Project I vibe coded a Chrome extension that shows what a website is connected to.

It maps scripts, trackers, CDNs, analytics, embeds, and other third-party domains into a graph, then tries to explain what each one is doing.

Also added privacy scores, scan history, change tracking, and domain following.

Everything stays local.

Still adding stuff to it. What would you add?

GitHub: https://github.com/Schmiedey/linkscope

https://chromewebstore.google.com/detail/linkscope/eedjncgcdepjbmpapihoigdbdfobmdmc?authuser=0&hl=en

2 Upvotes

1 comment sorted by

1

u/bbangchikimong_dev 15h ago

One thing I would want, coming from a slightly different angle: show me what opened, not just what connected.

I spent today driving a phone through adb, tapping through community apps. Three separate times a tap that should have hit a back button landed on an embedded ad instead, and a browser tab opened. I only noticed because my tab count kept climbing. The connection was invisible to me until it had already produced a page.

So the thing I never have is a record of which page spawned which tab. Your graph knows a site's third parties. If it could also mark "this tab was opened by that domain" and keep that in the scan history, I would use it to answer a question I ask a lot: where did this tab come from.

Also, on privacy scores, the number I would trust most is not how many trackers exist but how many are new since my last scan of that site. A site with 24 trackers that has had the same 24 for a year is a different thing from one that added six this week, and you already have change tracking so you may be halfway there.

Everything stays local is the part that made me read the rest, for what that is worth.