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.
API tokens for Blablador, issued after Helmholtz/JSC sign-in
Translation pending
SecurityPython · JavaScriptGitHub @HelmholtzAI-FZJOnlineOwner 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
API tokens for Blablador, the Helmholtz AI LLM service: JSC Login (OAuth) sign-in, self-service tokens, a validation API for the gateway
Taken from the repository README
Loading the full README.
Read the full README ↗The Token Generator issues the API tokens people use to call Blablador, the LLM service of Helmholtz AI at Forschungszentrum Jülich. People sign in with JSC Login (Unity-IDM, OAuth 2.0), create personal tokens on a dashboard, and the Blablador API gateway checks each presented token with this service.
Documentation: https://helmholtzai-fzj.github.io/blablador-token-generator/
uv sync --frozen --all-extras
cp config.yaml.example config.yaml # then follow the getting-started guide
./start.sh development # http://127.0.0.1:8080
Getting started
explains the development configuration and how to create the first
administrator (python -m app.manage create-local-admin).
curl -X POST https://tokens.example.org/api/v1/auth/validate \
-H "Authorization: Bearer blablador-…"
# 200 {"valid": true, "user_id": "…", "expires_at": "…+00:00", "error": null}
# 401 for unknown, revoked or expired tokens
See the API reference.
Production runs on Kubernetes with the Helm chart in
helm/blablador-token-generator: the
application, a hardened PostgreSQL and Redis, all over verified TLS, with
network policies and optional nightly backups. Docker Compose is supported for
single hosts. Start with the
production checklist.
Images for the production cluster live in the JSC registry
(registry.jsc.fz-juelich.de/kaas/rke2-clusters/blablador/). Tagged releases
are built, scanned and published by CI to ghcr.io/helmholtzai-fzj/, and to
the JSC registry when its credentials are configured.
uv run pytest # tests (SQLite; set TEST_DATABASE_URL for PostgreSQL)
uv run --only-group lint ruff check . # lint
uv run --only-group docs mkdocs serve
Schema changes are Alembic migrations in app/migrations/; see
Development.
Changes are recorded in CHANGELOG.md.
Report vulnerabilities privately, as described in SECURITY.md.
The October 2026 security audit, with its threat model, control inventory and
evidence, is in security_audit/.
MIT, see LICENSE.