🛡️ BLA (Blind LLM Agents) — Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.
JavaScript adversarial-aiclaude-codecursorelectron-securityllm-securitymcpmcp-serverobfuscationreverse-engineeringwebassembly
docs: align Node engine, release model, and benchmark figures with code
DeryFerd524b9c1a6db3
diff --git a/AGENTS.md b/AGENTS.mdindex b6f9da7..ba87b40 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -8,7 +8,7 @@ This repository contains **BLA (`bla-agents` — Blind LLM Agents)**, an open-so- `src/core/`:- `types.ts`: Domain interfaces (`AuditReport`, `ProtectionResult`, `VerificationReport`, `BenchmarkReport`).- `detector.ts`: Magic-byte and file-extension format detection across 19 artifact types (including JS/TS, `.asar`, `.wasm`, `.py`/`.pyc`, ELF/Mach-O/PE, `.sqlite`, `.safetensors`, `.gguf`, `.dex`, and `Il2Cpp` metadata).- - `sqlite-runtime.ts`: Lazy `node:sqlite` `DatabaseSync` loader validating Node `^22.13.0 || >=24.0.0`.+ - `sqlite-runtime.ts`: Lazy `node:sqlite` `DatabaseSync` loader validating Node `^22.23.4 || >=24.0.0`.- `output-path.ts`: Safe output path admission checks (`assertSafeOutputPath`).- `release-exposure.ts`: Bounded read-only source-map & symbol exposure scanner (`inspectReleaseExposure`).- `prng.ts`: Deterministic xorshift/mulberry32 PRNG (`SeededPrng`).diff --git a/README.md b/README.mdindex 8c722c9..ed16104 100644--- a/README.md+++ b/README.md@@ -158,7 +158,7 @@ We do **not** claim those paths are empirically bankrupt until `redteam:rea` (or`npx bla-agents benchmark` runs a **local Counter-REA showcase**: exposure scores, **estimated** token/cost multipliers, and **measured** runtime equivalence. Token/$ columns are **internal estimates** derived from BLA's catalog of REA limits — they are **not** the same as the empirical REA process measurements above (those are byte-level analyzer failures with real error strings). `npm run verify:rea` is a **constant-drift harness only** and must never be cited as protection evidence; the only authoritative gate is `npm run redteam:rea`.-Latest local run (bla-agents **v1.4.0**): aggregate **~612.5×** tokens · **~292.2×** cost · **14/14** runtime-exact.+Latest local run (bla-agents **v2.1.0**): aggregate **~639.5×** tokens · **~304.4×** cost · **14/14** runtime-exact.| Target | Unprotected (est.) | Protected (est.) | Token mult (est.) | Runtime || --- | --- | --- | ---: | :---: |diff --git a/STATE.md b/STATE.mdindex 53f4344..9043469 100644--- a/STATE.md+++ b/STATE.md@@ -2,7 +2,7 @@**Version:** 2.1.0 (`package.json` ↔ `src/identity.ts`, verified by build; see `CHANGELOG.md`)**Status:** CI matrix runs typecheck, build, tests and the benchmark on ubuntu / macos / windows with Node 24. Windows checkouts keep `challenge/**` LF via `.gitattributes` so the CrackMe seals verify.-**Publishing:** tag-only releases (`git tag bla-agents-<version>`); see `CHANGELOG.md` and GitHub Releases.+**Publishing:** tagged releases (`git tag bla-agents-<version>`) plus GitHub Releases. The release workflow can also publish the packed tarball to npm with provenance when `NPM_TOKEN`/OIDC is configured; a release cut may intentionally skip the npm step (see `CHANGELOG.md`).## One-sentence usagediff --git a/docs/installation.md b/docs/installation.mdindex 414168e..fac11f5 100644--- a/docs/installation.md+++ b/docs/installation.md@@ -1,6 +1,6 @@# Installation & Setup Guide-**BLA (`bla-agents` — Blind LLM Agents)** is distributed as a zero-config Node.js CLI and MCP server that runs anywhere Node.js `^22.13.0 || >=24.0.0` is installed.+**BLA (`bla-agents` — Blind LLM Agents)** is distributed as a zero-config Node.js CLI and MCP server that runs anywhere Node.js `^22.23.4 || >=24.0.0` is installed (matches `package.json` `engines`).---