While moving some todos from one location to another I came across “Check Site Inspector” and thought, why not run it against this website right now – how hard can it be.
Not that hard it turns out.
💸💸 Triplechecker
The git repository has been archived since January 2025 and they basically point you towards www.triplechecker.com which is their cloud deploy.
It worked very well… Finding a whopping 100 spelling errors on itenium.be, but after the first 7 errors, it asked me to sign up for a mere €15/month. Uhm, no thanks.
Docker Container
You can pretty easily host it yourself though!
git clone https://github.com/siteinspector/siteinspector
cd siteinspector
# Open docker-compose.yml, search for "SECRET_KEY_BASE:"
# and enter a random 30+ character key.
docker compose up -d
Surf to http://localhost:808
📈 Profit!!
Big oopsie
So one of the 100+ typos it found was on our home page, in the very first slide, a typo which has been screaming at our customers on our website for 8 years. Whoops!
(strenghten vs strengthen)
Heh heh, maybe no one ever noticed? 😬🙈🤫
Let AI figure it out
Since the siteinspector README just points you towards the paying service, I had the brilliant idea of asking AI to figure it out for me!
Prompt: https://github.com/siteinspector/siteinspector
You know this one? Know how I can run it against my website?
Yes! siteinspector is a Ruby gem that audits websites for things like redirects, headers, security, and more.
Here’s how to run it against your website:
✅ 1. Install Ruby (if needed)
✅ 2. Install siteinspector gem
✅ 3. Run it against your site
gem install siteinspector
siteinspector https://itenium.be
AI Slopsquatting
ERROR: Could not find a valid gem 'siteinspector' (>= 0) in any repository
ERROR: Possible alternatives: site-inspector
That’s right, the gem doesn’t exist. And site-inspector is something different.
benbalter/site-inspector: Ruby Gem to sniff information about a domain’s technology and capabilities.
It was a potential slopsquat attack; an emerging danger of AI!
Let’s use the same steps mechanism it used on me to run a potentially disastrous command to illustrate.
✅ 1. AI hallucinates some dependency that looks real.
✅ 2. A malicious party registers this dependency and puts malware in it.
✅ 3. An unsuspecting developer runs the command and 💥
Extras
Other interesting reads