About
Made by one person, in the open.
WardenOne is an independent, open-source project by iri. It brings browser protection, practical controls and local visibility together in one extension, and it's built to explain itself.
Why it exists
Feeling safe online shouldn't take five extensions.
If you care about privacy and security, you probably know the routine. An ad blocker, then a tracker blocker, then something for scams, maybe a download checker if you're being careful. Each one does its own little job, none of them talk to each other, and none of them really explain themselves.
I wanted one extension that does the whole job properly and shows its working. When it steps in, you can see what it did and why. When it isn't sure, it says so instead of guessing.
And it shouldn't cost you anything, not money and not your data. There's no account, no tracking, and nothing gets sent back to me.
The name
Why “WardenOne”?
Warden is the job
A good warden keeps watch quietly and only steps in when something is genuinely wrong. That's the goal: stay out of your way, act on real evidence, and never claim to know more than it does.
One is how it's built
Every part of WardenOne reports to the same place. A shady redirect can inform a scam warning, a download can borrow what's known about the page it came from, and when a site breaks you can follow one record straight back to the decision that caused it.
It doesn't mean one extension can stop everything bad on the internet. Nothing can, and I'd rather be honest about that than promise you magic.
How it's built
Built slowly, tested properly, fixed in the open.
WardenOne runs in my own browser while I build it, so I'm usually the first to find out when something breaks. A lot of my time goes into poking at one stubborn site until it behaves, then making sure the fix doesn't break three others.
Nothing ships until it gets through the project's gate: 385 automated test suites, plus checks that generated files still match the source they're built from. When I get something wrong, the fix goes up in public, mistakes and all.

What guides it
Useful, inspectable protection.
Inspect the implementation
WardenOne's own code is public under the GNU GPL v3 or later. Third-party lists, data and assets keep their own licenses and notices.
Make data flows explicit
No WardenOne account and no telemetry. The privacy policy names every automatic request and every optional provider.
Respect the site you meant to use
Protection that breaks a legitimate page is a bug. It needs investigating, scoped rules and a way to recover.
Why the source matters
Someone once copied WardenOne to spread malware.
In August 2026 someone republished the project under another account and pointed its downloads at a credential stealer. GitHub took the account and site down. A security extension has a lot of access to your browser, so where you got it from really matters.
Releases only ever come from github.com/iri-dev/WardenOne, and WardenOne is never an installer.
It wasn't from me. The incident page has the file details, antivirus results and recovery steps.
Read the incident noticeWho makes it
Hi, I'm iri (it's pronounced eye-ree), and please just call me iri. It started as a cute little nickname with my friends, and I love it. There's no company or team behind WardenOne. Just me, far too many open tabs, and a stubborn belief that software should treat people with respect.
If something breaks, or you think I've got something wrong, please tell me. I'd honestly rather hear the hard stuff than collect polite compliments.
And take your time with it. Read the code, poke at it, ask me anything. I'll be here, probably fixing one more thing. 💜
Say hello
My inbox is always open.
Got a question, an idea, or just want to say hi? I read every message myself and reply when I can. If WardenOne broke a site, a GitHub issue is even better, because then anyone else hitting the same problem can find it too.
Discord
Add me as iri.dev
Buy me a coffee
Everything I make stays free. If you'd like to help anyway, there's a tip jar.
Found a security problem in WardenOne itself? Please use a private vulnerability report instead, so it isn't public before it's fixed.
Help make it more useful.
Report a bug, suggest an improvement, or read the source on GitHub.