Help Us Build This
Get Early Access
We'll send you updates as we add features and improve LogicStamp
LogicStamp is live, and we're looking for early users to help us improve
LogicStamp is currently built and maintained primarily by Amit Levi, with early contributions from the community. I'd love more collaborators - your feedback and ideas directly shape what we build next.
πΊοΈ Roadmap
Here's what we're building next. Your feedback will help us prioritize what matters most.
Recent Achievements
v0.6.0 (Current)
- Runtime schema validation (AJV-enforced) -
.uif.jsoncontracts are now validated during load. Invalid, malformed, or outdated contracts are rejected with capped, structured error reporting (max 20 errors) - Fail-closed contract loading - If the schema fails to load, contracts are rejected instead of silently bypassing validation
- Hardened contract loader error handling - Explicit distinction between file-not-found, read errors, JSON parse errors, and schema validation failures
- Path traversal protection - Enforced strict project-root boundaries across internal file utilities
- File lock race condition fix - Prevents concurrent lock acquisition mid-write
- Dependency security updates -
glob@13.0.6(patched minimatch ReDoS),ts-morph@27.0.2with improved TypeScript 5.x support - β οΈ Node.js >= 20 required - Required by dependency and security updates
- Test coverage expansion - Added root-boundary traversal tests and expanded extraction coverage
v0.5.5 (February 2026)
- State-based strict watch diffing - Strict watch mode now compares current state vs the original baseline (like
git diff), not cumulative history. Violations reflect current drift only and are automatically cleared when changes are reverted - Removed missing dependencies from strict watch violations - Third-party packages are no longer treated as breaking changes in strict watch mode
- Watch mode cleanup on exit (Windows/Cursor reliability) - Signal handlers register at watch startup, watch status paths resolve to absolute paths, synchronous cleanup runs on
process.on('exit'), and MCP tools remove stale status files when PID validation fails - Watch mode revert correctness - If
pack()fails during incremental rebuild, bundles/contracts/manifest now revert consistently - Resilient glob pattern failure handling -
globFiles()now continues across pattern failures, returns partial results when possible - Config read/write race condition (TOCTOU) fixed - Added lightweight file locking using exclusive lockfiles + PID tracking
- Atomic writes to prevent crash corruption - Config + status writes now use temp-file + rename pattern
v0.5.4 (February 2026)
- Graceful shutdown on process exit - Introduced a centralized cleanup registry so watchers/status files are reliably cleaned up on errors and signals (SIGINT/SIGTERM/SIGHUP)
- Token comparison fails loudly when all bundles fail - Added
checkBundleResults()to detect complete failure for--compare-modes - Improved debug logging for unresolved dependencies
- Reduced duplicated error handling in config writes
v0.5.3 (February 2026)
- Bug fixes - Fixed JSON schema validation (removed incorrect required fields), race condition in sanitization stats, memory leak in global caches, and Windows path separator bug in dependency resolution
- Performance improvements - O(nΒ²) to O(n) in dependency collection (replaced
array.shift()with index-based iteration), eliminated redundant file reads in token estimation via caching - Type safety - Replaced unsafe
as anycasts with proper ts-morph type guards across 10+ files
v0.5.2 (February 2026)
- JSON Schema completeness - Added missing fields to JSON schema (
nextjs,antd,chakraUI,shadcnUI,radixUI) that were causing IDE validation errors
v0.5.1 (February 2026)
- Chakra UI support - Complete style metadata extraction for Chakra UI components
- Ant Design support - Complete style metadata extraction for Ant Design components
v0.5.0 (January 2026)
- Strict watch mode (
--strict-watch) - Track breaking changes and violations during watch mode. Automatically detects breaking changes when files are modified (removed props, events, state, functions, variables; changed prop types; removed contracts; missing dependencies). Real-time violation reporting with cumulative tracking across watch sessions. Writes structured JSON violation reports and provides CI-friendly exit codes - Schema improvements - Renamed fields for clarity:
MissingDependency.versionβpackageVersion,UIFContract.versionβcomposition,UIFContract.logicSignatureβinterface. These changes improve clarity and avoid confusion between component composition and version numbers - Performance optimizations - O(1) dependency collection lookups and missing dependency tracking. Replaced O(n) linear searches with Map-based and Set-based lookups for significantly improved performance on large projects
- Watch mode improvements - Fixed race condition in watch mode using Promise-based locking. Fixed silent error swallowing in compare handler
v0.4.1 (January 2026)
- Watch mode - Automatic context regeneration when source files change. Incremental rebuilds only regenerate affected bundles. Detects and displays contract changes (props, hooks, state, events). Debounces rapid changes. Watches style files when using
--include-style. Debug mode shows hash changes. Status files for tooling integration
v0.4.0 (January 2026)
- Backend framework support - Comprehensive support for Node.js backend frameworks (Express.js, NestJS). Extracts API routes, HTTP methods, route parameters, request/response types, and framework-specific metadata. Automatically detects backend frameworks and skips frontend extraction for backend files. Introduces new
node:apicontract kind and extensiblelanguage:typepattern for future language support
v0.3.10 (January 2026)
- Advanced Next.js App Router features - Enhanced Next.js metadata extraction with route roles, segment paths, and metadata exports. Automatically detects route roles (
page,layout,loading,error, etc.), extracts segment paths from file structure, and parses both static and dynamic metadata exports
v0.3.9 (January 2026)
- Dynamic Tailwind class parsing (Phase 1) - Enhanced Tailwind CSS extractor to resolve dynamic class expressions within template literals. Resolves const/let variables, object properties, and conditional expressions. Handles ~70-80% of common dynamic class patterns
v0.3.8 (January 2026)
- Enhanced third-party component info (Phase 1) - Missing dependencies now include package names and versions for third-party packages. Package name extraction handles scoped packages and subpath imports. Version lookup reads from package.json with caching for efficiency
v0.3.7 (January 2026)
- Emit detection accuracy - Fixed issue where internal event handlers were incorrectly listed as component emits. Now only includes handlers that are part of the component's public API (props)
v0.3.6 (January 2026)
- Hook parameter detection - Comprehensive support for extracting function signatures from custom React hooks
- Default depth changed from 1 to 2 for better nested component signature extraction
v0.3.5 (January 2026)
- Styled JSX support with full CSS extraction
- Enhanced inline style extraction
v0.3.4 (January 2026)
- Vue.js TypeScript/TSX support - Comprehensive Vue 3 Composition API support
Earlier Releases
- MCP Server Integration - Available now! Get started
- Style metadata extraction (Tailwind, SCSS, Material UI, ShadCN, Radix UI, Framer Motion)
- Security scanning and secret sanitization
- TOON output format
High Priority Bug Fixes
Dynamic Class Parsing (Phase 2)
Resolve advanced variable-based classes within template literals. Phase 1 complete (v0.3.9) - handles const/let variables, object properties, and conditional expressions (~70-80% of patterns). Phase 2 will handle object lookups with variables, cross-file references, and function calls returning class strings (~15-20% of edge cases).
Framework Expansion
JavaScript & JSX Support
Add support for JavaScript (.js) and JSX (.jsx) files in addition to TypeScript. Support JSDoc type annotations for type inference.
Complete Vue.js Support
Add full support for Vue Single File Components (.vue files). Parse template, script, and style blocks. Support both Options API and Composition API.
Watch Mode
Automatic context regeneration when source files change. Incremental rebuilds only regenerate affected bundles. Change detection shows what changed (props, hooks, state). Debouncing batches rapid changes. Status files for tooling integration.
MCP Server Enhancements
Semantic Component Search
Add semantic search across component bundles. Search by component descriptions, prop names, functionality, or metadata rather than requiring exact file/component names.
Git Baseline Support
Enable comparison against git commits/branches using baseline: "git:<ref>" syntax. This enables CI/CD integration and better change tracking.
Configuration File Support
Support mcp-config.json to set default values for profile, mode, paths, and other settings. Reduces parameter repetition and enables project-specific defaults.
Progress/Status Reporting
Add progress reporting for long-running operations like refresh_snapshot and compare_modes. Use MCP progress notifications to provide real-time updates.
Medium Priority Improvements
Future Enhancements
Performance & Optimization
- β Incremental bundle caching - Complete (v0.4.1) - Only regenerates changed bundles in watch mode
- Output size optimization - Further reduce token counts while maintaining accuracy
Framework Expansion
- Svelte support - Parse
.sveltefiles - Python support (experimental) - Expand beyond JavaScript/TypeScript ecosystems
- Java support (experimental) - Enterprise Java codebases
Developer Experience
- Integration examples for popular AI assistants
- Advanced debugging tools and diagnostics
- Custom profile configuration and overrides
This roadmap is actively maintained. This is a solo project, so priorities will shift based on what I learn from early users.
For the complete roadmap with detailed implementation plans, see CLI ROADMAP.md and MCP ROADMAP.md
Looking for contributors! If you're interested in helping build LogicStamp, check out the contributing guide or reach out directly.
Repositories: CLI β’ MCP Server
Who Should Join?
We're looking for developers who use AI assistants and want to help us make this better
Developers Using AI Assistants
If you're already using Cursor, Copilot, or Claude regularly, you probably know the pain of managing context. Help us make it better.
Teams with React/TypeScript Codebases
LogicStamp works best with React and TypeScript right now. If that's your stack, we'd love to see how it works for your team.
Open Source Maintainers
If you maintain an open source project, we think LogicStamp could help contributors understand your codebase faster. We'd love to test this theory.
People Who Like Trying New Tools
If you enjoy being an early adopter and don't mind the occasional rough edge, we'd love your feedback. We're responsive and actually listen.
Contributors Welcome
This is a solo project, and I'm actively looking for contributors! Whether it's bug fixes, new features, or documentation improvements, your contributions are welcome. Check out the contributing guide to get started.
Developers with Large Codebases
If you're working on a large codebase where context management is a real challenge, LogicStamp could help. We're especially interested in feedback from projects with complex architectures or many components.
Want to Help Us Build This?
We're just getting started. Your feedback will help us figure out what to build next.
Open source CLI β’ Free to use β’ Built with your feedback β’ Looking for contributors