Frequently Asked Questions
Common Questions About BLA (`bla-agents`)
Why does BLA use a Blue theme?
In security engineering, offensive and reverse-engineering tools are traditionally associated with Red Team workflows, while defensive protection tools represent Blue Team workflows. BLA (
bla-agents) focuses on the defensive side: auditing exposure and protecting release artifacts.
Does BLA affect runtime performance or change program output?
No. Static budget guards and call-graph state machines are placed behind O(1) bitwise invariants (such as
(Math.imul(x, x + 1) & 1) === 0) inside unreachable branches, so hot-path execution remains unchanged.
How do I run the full protection workflow in one step?
Run
npx bla-agents@latest defend ./dist --manifest from your terminal, or ask your connected coding agent to call the bla_defend MCP tool. It executes release exposure checks, auditing, protection, and verification in sequence.
Does BLA preserve existing GGUF model tensors and binary checksums?
Yes.
protectGgufBuffer preserves all original GGUF v2/v3 KV entries and trailing tensor slices while appending metadata entries, and Android DEX protection recomputes both the 20-byte SHA-1 signature and Adler32 checksum.