๐Ÿ”’ VhyxSeal
GitHub

Changelog

All notable changes to VhyxSeal packages. Most recent release first.

1.0.0-rc.1

2026-05-26Latest

Added

  • Complete semantic contract layer for web UI components
  • @vhyxseal/core โ€” zero-dependency foundation with contract schema, inference engine, security layer, manifest generator, relationship/capability registries, action tokens, key management
  • @vhyxseal/react โ€” React 18+ adapter with SealProvider, withAgentContract HOC, useContract / useCapability / useAgentAction hooks
  • @vhyxseal/vue โ€” Vue 3 adapter with VhyxSealPlugin and composables
  • @vhyxseal/vanilla โ€” Web Components adapter (SealButton, SealInput, SealForm, SealNav, SealDisplay, SealConfirmation)
  • @vhyxseal/nextjs โ€” Next.js integration with vhyxsealPlugin(), handleManifestRoute(), handleDashboardRoute()
  • @vhyxseal/devtools โ€” Development panel and contract overlay
  • @vhyxseal/cli โ€” CLI tools: simulate, verify, audit, init
  • @vhyxseal/testing โ€” Test utilities: matchers and drift detection
  • @vhyxseal/style โ€” CSS design tokens for VhyxSeal tooling
  • HMAC-SHA256 manifest signing with key management
  • Single-use action tokens with 6-step verification
  • Domain verification with HMAC-signed tokens
  • Injection detection across 14 pattern categories
  • DevTools audit dashboard at /__agent__/dashboard.json
  • Chrome DevTools extension (Manifest V3)
  • RFC-0001 open for community comment

Security

  • Default agent policy is deny (allowedAgents: [])
  • Timing-safe HMAC comparison throughout
  • crypto.randomBytes for all token generation

Known Limitations

  • Rate limit enforcement: schema defined, AgentPolicy.rateLimits middleware pending (1.1.0)
  • Registry backend: local only, hosted registry planned for future release
  • Multi-framework contract inheritance: planned โ€” cross-framework registry not yet available

VhyxSeal follows semantic versioning. Within a major version, changes are additive only โ€” fields are never removed or renamed. Breaking changes require a major version bump and the RFC process with a 12-month migration window. See RFC-0001 ยง7 Versioning Commitment for the full policy.