Changelog
All notable changes to VhyxSeal packages. Most recent release first.
1.0.0-rc.6
2026-10-03LatestChanged
@vhyxseal/devtoolsand the browser extension use the current Vhyxara icon drawings for lock, check, cross and alert; the extension's Refresh button draws an icon instead of a text glyph. The packages keep their own inline SVGs and still depend on nothing else.
1.0.0-rc.5
2026-09-28Fixed
@vhyxseal/devtools, the audit dashboard and the extension panel draw small inline SVG status icons with accessible labels instead of emoji.@vhyxseal/cliprints plain-text status symbols (✔ ! ✖ i) in its existing colours; emoji rendered inconsistently across terminals and broke column alignment.
1.0.0-rc.4
2026-09-27Fixed
- Every generated manifest now references
https://vhyxseal.com/schema/<version>. Manifests, thevhyxseal initmessage and package metadata pointed at a domain the project does not own. @vhyxseal/vanillais safe to import during server-side rendering (Next.js, Nuxt, Astro); it no longer extendsHTMLElementat module load outside the browser.
Changed
- A README for every published package, plus description, keywords, homepage, repository and issue links on npm.
- Requires Node 20.19 or newer (
engines.node), needed torequire()the ESM builds.
1.0.0-rc.3
2026-09-26Security
signManifest/verifyManifestdo real HMAC-SHA256 over a canonical manifest payload, replacing the placeholder signature; weak keys and legacy placeholder signatures are rejected. AddsattachSignatureandcanonicalManifestPayload.
Added
- A real
vhyxsealCLI binary withinit,simulate,verifyandaudit, plus newdiff(detects changes that break agents),keygen,sign/verifyandvisualize(draws a manifest as an animated VhyxChart flow).
Fixed
@vhyxseal/coreworks in the browser: SHA-256, HMAC-SHA256 and random ids useglobalThis.cryptoinstead of importing Node'scrypto, which broke browser bundles. Checked against the FIPS and RFC 4231 test vectors.withAgentContractforwards refs and warns once per contract id.SealProviderfalls back to the current host when the domain is empty, memoises inline config objects, and no longer readsprocess.envunguarded.- Package exports list
typesfirst with arequirecondition;@vhyxseal/coreno longer advertises a missing CommonJS build.
1.0.0-rc.2
2026-05-29Added
defineContractTemplate()— a contract without anid, for component libraries whose instance ids are added at render time. Templates are frozen and fingerprinted, and identical templates share a fingerprint.
1.0.0-rc.1
2026-05-26Added
- 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,withAgentContractHOC,useContract/useCapability/useAgentActionhooks@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 withvhyxsealPlugin(),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.randomBytesfor all token generation
Known Limitations
- Rate limit enforcement: schema defined,
AgentPolicy.rateLimitsmiddleware 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.