BLA
BLA (Blind LLM Agents) is the open-source Blue Defense MCP and CLI built to protect software artifacts against automated AI reverse-engineering workflows.
The open, categorized directory of the web's bots — user agents, IP ranges, and how to verify them.
SecurityTypeScript · AstroGitHub @mayankguptadotcomOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The open, categorized directory of verified good bots — identities, user agents, IP ranges, and verification recipes. verifiedbots.dev
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
The open, categorized directory of verified good bots — identities, user
agents, IP ranges, and machine-actionable verification recipes — at
verifiedbots.dev.
No canonical open source project joins bot identity (who operates this
thing, what category is it) with both UA patterns and authoritative
verification data. Bot directories tend to withhold IP ranges; IP-range
lists tend to lack identity and category context. This repo is that join,
done in the open, refreshed daily, with the provenance to back it up.Read the full README ↗The open, categorized directory of verified good bots — identities, user agents, IP ranges, and machine-actionable verification recipes — at verifiedbots.dev.
No canonical open source project joins bot identity (who operates this thing, what category is it) with both UA patterns and authoritative verification data. Bot directories tend to withhold IP ranges; IP-range lists tend to lack identity and category context. This repo is that join, done in the open, refreshed daily, with the provenance to back it up.
bots/*.yaml — one curated entry per bot (schema:
src/schema/bot.schema.json), covering identity, category, behavior, and
verification recipes.dist/ — built artifacts, also served live from verifiedbots.dev under
/data/ (see "Use the data" below).PRACTICES.md — the Good Bot Practices standard every entry is measured
against.All artifacts are served live and CC-BY-4.0 licensed:
https://verifiedbots.dev/data/all.json — the full datasethttps://verifiedbots.dev/data/by-category/<category>.json — one categoryhttps://verifiedbots.dev/data/by-tier/tier-<n>.json — one verification
tier (1 fully verifiable, 2 verifiable, 3 listed only)https://verifiedbots.dev/data/bots/<id>.json — one bothttps://verifiedbots.dev/data/ips/<id>.ips — one bot's IP rangeshttps://verifiedbots.dev/data/ips/by-category/<category>.ips — one
category's verified IP rangeshttps://verifiedbots.dev/data/ips/by-tier/tier-<n>.ips — one tier's
verified IP rangeshttps://verifiedbots.dev/data/ips/all.ips — every verified IP rangehttps://verifiedbots.dev/data/ua-patterns.json — user-agent match
patterns for every bothttps://verifiedbots.dev/rss.xml — RSS feed of newly added botsSee CONTRIBUTING.md for how to add or update a bot entry, and PRACTICES.md for the standard entries are measured against.
npm test, npm run validate, and npm run build:artifacts cover the data
pipeline; see CONTRIBUTING.md for the full local setup
(including the site/ Astro app). Deploy/ops notes live in
docs/DEPLOY.md.
Code: MIT (LICENSE). Data (bots/, dist/): CC-BY-4.0 (LICENSE-DATA.md).