All posts

BonkLM 1.0 is on npm

The 1.0 line is live under @blackunicorn: fifty-two packages at one version, a frozen twelve-layer API, and an Apache-2.0 core.

BonkLM is on npm. npm install @blackunicorn/bonklm now resolves to the 1.0 line, published under the @blackunicorn scope. Fifty-two packages ship together at one version — the core engine plus the framework, provider, agent, RAG, and memory connectors — so a project never has to reconcile a matrix of package versions.

What 1.0 actually froze

The 1.0.0 release promoted the release-candidate line to a stable, frozen public API. The detection surface it locked in is the twelve-layer set: the original inbound validators and outbound guards, plus four layers added at GA —

  • Harm intent — deterministic harm-goal detection with no LLM judge in the path, evaluated over several de-obfuscated views of the input.
  • Social engineering — credential-phishing and pretext-coercion detection.
  • Encoded rescan — decode base64, hex, ROT, leetspeak, and multi-layer chains, then rescan the revealed text.
  • Indirect injection — provenance-gated scanning of retrieved documents, tool results, and memory writes. It never fires on raw user text, so trusted human input stays lenient while untrusted content is held to a higher bar.

The engine stayed deterministic: pattern and structural checks, in-process, no second model in the hot path. Every verdict is reproducible, and every block leaves a tamper-evident trace.

The honest license story

The core is Apache-2.0, and has been since 1.0.0 (relicensed from MIT under ADR-0006). One detail worth stating plainly: the old 0.2.0 preview that sat on npm for months predates the relicense and is still MIT as a historical version. Installs now resolve to the Apache-2.0 1.0.x release; the legacy version is not the one you get.

The patches since

The 1.0.x patches that followed are almost entirely release-lane work — deterministic release bundles, provenance attestation, npm channel promotion that advances the whole family together. That is deliberate. A security library’s supply chain is part of its security posture, and we would rather spend a patch line making the publish reproducible than rush a feature.

Start here

The quick start installs the wizard and ships a first guardrail in about a minute. The playground runs the real validators against your own prompts, and the known-limitations page is the honest edge of what a deterministic engine catches.