v1.0.16

Release-Scope: family

BonkLM v1.0.16

Publish-lane completion.

Fixed

• The release bundle normalizer now reads GNU long-name (@LongLink) tar entries in addition to PAX overrides, so pack-and-verify agree on the GNU-tar CI image.
• Staging container cleanup no longer fails a completed publish: GHCR refuses manifest deletions for the Actions identity (UNSUPPORTED — a token-scope limitation), which is now warned on and left to retention. See CHANGELOG.md.

v1.0.15

Release-Scope: family

BonkLM v1.0.15

Deterministic release bundles.

Fixed

• Packed release tarballs now carry deterministically serialized manifests (sorted dependency maps,
  sorted archive entries, fixed metadata), making the release bundle a pure function of the source
  tree and publish-lane reruns idempotent. See CHANGELOG.md.

v1.0.14

Release-Scope: family

BonkLM v1.0.14

Peer-floor alignment, and the release lane's channel promotion is fixed.

Changed

• Peer dependency floors now match the security overrides this workspace pins
  (bonklm-mcp → @modelcontextprotocol/sdk ^1.25.2, bonklm-nestjs → @nestjs/common and
  @nestjs/core ^11.1.18, bonklm-hono → hono ^4.12.34, bonklm-nextjs → next
^16.2.11). These peers are declared optional, so a consumer below a new floor normally sees a
  warning rather than a failed install; a resolver run with strict peer dependencies will error.

Fixed

• The npm channel promotion no longer fails when a package carries a prerelease latest value it
  never promoted. npm sets latest itself on a package's first publish even under --tag, and
  those values were treated as promoted state, so the promotion refused before moving any dist-tag.
  They are now overwritten by the promotion and logged. A stable value on next remains a hard
  stop, and mixed or rollback promotions remain refused.
• Channel reads tolerate registry lag and transient failures, while a channel refusal or differing
  published bytes surface immediately; a version that has not propagated yet is treated as lag
  rather than as an integrity mismatch.
• Container staging cleanup no longer fails the release transaction when cosign reports that there
  is nothing left to remove.
• Local-harness settings-integrity baseline matches the tracked hook count again.
• Regenerated the core package's tarball-drift snapshot, which had gone stale against the connector
  catalog.

See CHANGELOG.md for the
full history.

v1.0.13

Release-Scope: family

BonkLM v1.0.13

Promotion resilience — the fully-shipped line.

Changed

• The promotion final channel verification retries with backoff (registry dist-tag reads lag writes).
• All prior 1.0.x hardening included (detection, auth, supply chain, lane tooling; vector connectors as @blackunicorn/bonkdrant and @blackunicorn/bonkviate).

v0.2.0 - BonkLM: LLM Security Guardrails

BonkLM v0.2.0 Release Notes

Release Date: February 23, 2026

Overview

BonkLM v0.2.0 is a significant update that includes a complete project rebranding, enhanced security features, and improved connector ecosystem. This release focuses on security hardening, better developer experience, and expanded platform support.

What's New

Project Rebranding

• New Name: The project has been renamed from LLM Guardrails to BonkLM
• New Package Scope: All packages now use the @blackunicorn/bonklm namespace
• CLI Commands Updated: All CLI commands now use bonklm instead of llm-guardrails

Security Enhancements

Attack Logger (New Feature)

• Comprehensive attack logging system for security monitoring
• Configurable logging levels and output formats
• Structured attack data capture for analysis and forensics
• Located in packages/logger

Core Validation Hardening

• Enhanced prompt injection detection with improved pattern matching
• Strengthened jailbreak detection algorithms
• Better boundary detection for adversarial inputs
• Improved PII (Personally Identifiable Information) validation

Connector Updates

All connector packages bumped to v1.1.0 with:

• Improved error handling and resilience
• Better timeout management
• Enhanced credential validation
• Updated dependencies for security

Updated connectors:

• @blackunicorn/bonklm-anthropic v1.1.0
• @blackunicorn/bonklm-chroma v1.1.0
• @blackunicorn/bonklm-copilotkit v1.1.0
• @blackunicorn/bonklm-express v1.1.0
• @blackunicorn/bonklm-fastify v1.1.0
• @blackunicorn/bonklm-genkit v1.1.0
• @blackunicorn/bonklm-huggingface v1.1.0
• @blackunicorn/bonklm-langchain v1.1.0
• @blackunicorn/bonklm-llamaindex v1.1.0
• @blackunicorn/bonklm-mastra v1.1.0
• @blackunicorn/bonklm-mcp v1.1.0
• @blackunicorn/bonklm-nestjs v1.1.0
• @blackunicorn/bonklm-ollama v1.1.0
• @blackunicorn/bonklm-openai v1.1.0
• @blackunicorn/bonklm-pinecone v1.1.0
• @blackunicorn/bonklm-qdrant v1.1.0
• @blackunicorn/bonklm-vercel v1.1.0
• @blackunicorn/bonklm-weaviate v1.1.0

Middleware Framework Improvements

• Express Middleware: Enhanced request/response handling
• Fastify Plugin: Improved integration patterns
• NestJS Module: Better decorator support and dependency injection

Quality & Testing

• 100% test pass rate across all packages
• 2003 passing tests
• Enhanced security test coverage
• Improved type safety across all packages

Package Versions

Package	Old Version	New Version
@blackunicorn/bonklm (core)	0.1.0	0.2.0
@blackunicorn/bonklm-logger	0.1.0	0.2.0
@blackunicorn/bonklm-wizard	0.1.0-deprecated	0.2.0-deprecated
All connectors	1.0.0	1.1.0

Security Fixes

This release includes security improvements to:

1. Command Injection Prevention: Enhanced validation in the wizard package to prevent command injection through PATH manipulation
2. DoS Protection: Added resource limits to prevent denial-of-service through resource exhaustion
3. Credential Handling: Improved secure credential handling in audit logs
4. Input Validation: Strengthened input validation across all validators

Breaking Changes

CLI Commands

If you were using the old llm-guardrails CLI commands, you'll need to update to bonklm:

# Old (v0.1.0)
llm-guardrails wizard
llm-guardrails status

# New (v0.2.0)
bonklm wizard
bonklm status

Package Imports

Update your imports to use the new package names:

// Old (v0.1.0)
import { GuardrailEngine } from '@llm-guardrails/core';

// New (v0.2.0)
import { GuardrailEngine } from '@blackunicorn/bonklm';

Migration Guide

Updating from v0.1.0

1. Update package names in your package.json:

   npm uninstall @llm-guardrails/core
   npm install @blackunicorn/bonklm

2. Update imports in your code:

   // Find and replace
   - from '@llm-guardrails/core'
   + from '@blackunicorn/bonklm'
   - from '@llm-guardrails/openai'
   + from '@blackunicorn/bonklm-openai'

3. Update CLI scripts in your package.json:

   {
     "scripts": {
   -    "setup": "llm-guardrails wizard"
   +    "setup": "bonklm wizard"
     }
   }

Installation

# Core package
npm install @blackunicorn/bonklm

# Connectors
npm install @blackunicorn/bonklm-openai
npm install @blackunicorn/bonklm-anthropic
npm install @blackunicorn/bonklm-express

# Logger
npm install @blackunicorn/bonklm-logger

Documentation

• Getting Started
• API Reference
• Connectors Guide
• Security Guide

Contributors

• Black Unicorn Security Team

Support

• GitHub Issues: https://github.com/blackunicorn/bonklm/issues
• Documentation: https://github.com/blackunicorn/bonklm#readme
• Security: security@blackunicorn.tech

License

MIT License - See LICENSE file for details