What's your response header content? Reads like it's being cf-mitigated.
Edit: loosened a cf rule, should be good now.
thetwopct 5 hours ago [-]
Interesting but Laravel usage seems so low. As Laravel uses React or Vue etc I feel like a site could be easily classified as React when it’s Laravel running the show.
datafreak_ 1 hours ago [-]
[flagged]
addedlovely 20 hours ago [-]
Nice one.
I've been doing the same bit wider scope, for the whole Crux list, pruned to apex domains, and looking for CMS signals - how's your throughput?
I'm not doing any headless browser stuff, or many requests, so hyper optimised for speed.
I do grab robots.txt - didn't really see much in llms.txt or humans.txt in the wild, does yours?
addedlovely 20 hours ago [-]
Ohh Cloudflare verified bot status, interesting I'll check that out.
I'm seeing about 6.6% block rate, but that does climb over time.
I'm a little surprised you can't see the analysis for StackScope itself!
Also, it'd be interesting to see the trend of vibe score over time.
datafreak_ 16 hours ago [-]
I'm trying but it's getting blocked by Cloudflare and ending up getting broken, ha!
I will include a vibe score trend in the next blog post.
8organicbits 13 hours ago [-]
Cool tool, I'm also surprised by how different the startup stacks are from the general Internet.
For HSTS, don't forget to check the preload list. Domains under .dev are all preloaded, for example, so they don't need to set the header for HSTS to apply.
idid 20 hours ago [-]
One extension, beyond stack: market category/domain/application - or any combo that tells me what the product does.
Fab project otherwise!
datafreak_ 20 hours ago [-]
[flagged]
bji9jhff 10 hours ago [-]
"Verified bot" for cloudflare sounds like "Acceptable ad" for adblock.
Gabriel_Valente 18 hours ago [-]
Nice one, looks interesting.
I didn't knew that Vercel was so far ahead on hosting.
People don't usually use Cloudflare Pages for hosting? Or it doesn't enter in that metric? https://stackscope.dev/trends/2026/06
Overall this looks solid
datafreak_ 18 hours ago [-]
Cloudflare Pages get hidden behind the CF CDN, so are included in the CDN figure.
Gabriel_Valente 18 hours ago [-]
right, makes sense
cpursley 16 hours ago [-]
Makes me sad how Nextjs has become the default for so many startups…
sandeepkd 16 hours ago [-]
Unfortunately the chances are that it would become cyclic with the increasing use of LLMs to generate code
GET https://stackscope.dev/css/stackscope.css?v=qkmEKPTNqImS7aeD... NS_ERROR_CORRUPTED_CONTENT
GET https://stackscope.dev/css/utilities.css?v=l7--cPr2cfIn6iDRB... NS_ERROR_CORRUPTED_CONTENT
GET https://stackscope.dev/css/page-extras.css?v=m-VKj9bQg7fMpFK... NS_ERROR_CORRUPTED_CONTENT
GET https://stackscope.dev/js/site.js?v=SxUp8zU6gnAArRwBXr22wIBS... NS_ERROR_CORRUPTED_CONTENT
Edit: loosened a cf rule, should be good now.
I've been doing the same bit wider scope, for the whole Crux list, pruned to apex domains, and looking for CMS signals - how's your throughput?
I'm not doing any headless browser stuff, or many requests, so hyper optimised for speed.
I do grab robots.txt - didn't really see much in llms.txt or humans.txt in the wild, does yours?
I'm seeing about 6.6% block rate, but that does climb over time.
I'm a little surprised you can't see the analysis for StackScope itself!
Also, it'd be interesting to see the trend of vibe score over time.
I will include a vibe score trend in the next blog post.
For HSTS, don't forget to check the preload list. Domains under .dev are all preloaded, for example, so they don't need to set the header for HSTS to apply.
Fab project otherwise!
Overall this looks solid