Repository navigation
Releases: eduardbar/drift
Release list
v1.7.0
[1.7.0] - 2026-08-13
Added
- Drift Guardian core: deterministic policy gate for git diffs (
src/guardian/). Includes the domain model (GuardianFinding,GuardianRule,GuardianPolicy,GuardianContext,GuardianResult,AIReviewProvider) and the git change collector (stdin / staged / base ref / diff file / working tree), reusing the existing unified-diff parser and git readers without new runtime dependencies. - Product and technical documentation for Guardian:
docs/guardian/(PRD, TRD, APP_FLOW, UI_UX_DESIGN_BRIEF, BACKEND_SCHEMA, IMPLEMENTATION_PLAN). - OpenSpec delta spec for the
guardiandomain underopenspec/specs/guardian/.
v1.6.0
What's Changed
- feat: AI integration foundation and context file command by @eduardbar in #33
- feat: MCP server for AI tool integration by @eduardbar in #35
- feat: add local AI guard for proposed diffs by @eduardbar in #37
- docs: complete local AI integration workflow by @eduardbar in #39
- chore(release): prepare v1.6.0 by @eduardbar in #41
Full Changelog: v1.5.0...v1.6.0
v1.5.0
Drift v1.5.0
This release finalizes the hardening cycle for merge/release confidence:
- mandatory quality matrix on Node 20/22 with reusable quality gates
- runtime/docs/performance policy checks (
check:runtime-policy,check:docs-drift,check:perf-budget) - smoke E2E gate and CI artifacts for smoke/perf diagnostics
- schema contracts for
doctor --jsonandguard --jsonwith$schema+toolVersion - CI/action version alignment guards and release metadata alignment
- test stability improvements (default timeout budgets)
See CHANGELOG.md for complete details.
v1.4.0
Release Notes Draft (S5)
Scope
This draft covers the latest trust-core and SARIF-related changes prepared for release packaging.
What changed
- Added/solidified release-facing CLI capabilities:
initfor project scaffolding and baseline bootstrap.doctorfor environment diagnostics.guardfor non-regression enforcement by diff or baseline.
- Consolidated output format behavior around
--formatand preserved legacy aliases for compatibility. - Added SARIF output coverage across critical commands (
scan,ci,diff,review,trust). - Aligned CI and action v2 contract expectations with SARIF-enabled workflows.
- Expanded tests and docs to reduce release risk in CLI output contracts.
User impact
- Teams can ingest drift findings in SARIF-native tooling without custom adapters.
- Trust/review automation in PRs is more consistent thanks to normalized output contracts.
- Onboarding and guardrail setup are faster with
init,doctor, andguard.
Risks and watch points
- SARIF consumers may still differ in strictness; validate in at least one real CI environment.
- Legacy alias paths (
--json,--comment,--markdown) depend on compatibility behavior and should remain covered by tests. - Trust/reporting flows rely on artifact path conventions in CI; keep workflow and docs synchronized.
Minimal validation before tag
- Smoke no-build commands:
scan --format sarifci --format sariftrust --format sarifreview --format sarif(ordiff --format sariffallback)
- Targeted tests:
tests/cli-sarif.test.tstests/format.test.tstests/sarif.test.ts
v1.3.0 - Trust gates, cloud governance, and low-memory guardrails
Highlights
- Added trust-first merge governance with diff-aware scoring, reusable
trust-gate, policy packs, and advanced trust guidance in CLI. - Added CLI-first KPI evidence loop with
drift kpi <path>for aggregate trust metrics from artifacts. - Expanded cloud-like local governance primitives: tenant boundaries, actor-based authz, plan lifecycle commands, and strict actor enforcement mode.
- Hardened plugin ecosystem contract with versioned validation, compatibility diagnostics, and duplicate rule checks.
- Improved scalability with low-memory analysis mode, guardrails, and benchmark tooling.
- Fixed diff integrity noise by normalizing issue matching across line endings, preventing false new/resolved churn in
review --baseandtrust --baseflows.
Notable Commands
drift trust ... --policy-pack <name> --explain-policydrift trust-gate <trust-json-file> --policy-pack <name> --branch <name>drift kpi <path>drift cloud plan-set|plan-changes|usagedrift scan --low-memory --chunk-size <n> --max-files <n> --max-file-size-kb <n>
v1.2.0
Release v1.2.0\n\nHighlights:\n- Added SaaS foundations with cloud ingest, summary, and dashboard commands\n- Introduced local cloud store model and usage metrics\n- Enforced free-phase guardrails with free-until-7500 policy\n- Added SaaS foundation test coverage\n- Updated PRD roadmap alignment for cloud foundations completion
v1.1.0
Release v1.1.0\n\nHighlights:\n- New drift review command for PR diff analysis\n- New drift map command generating architecture.svg\n- AI likelihood and AI code smell signals in AI output\n- Configurable architecture rules\n- Repository quality and maintenance risk metrics\n- Plugin system MVP\n- Extended fix preview/write modes\n- Product and contributor documentation updates
v1.0.0 — Stable Release
What's new in v1.0.0
26 detection rules across 6 phases
All rules are now fully tested and documented.
Full test coverage
131 tests passing — every rule has dedicated test cases including cross-file analysis (unused-export, dead-file, unused-dependency, circular-dependency, layer-violation, cross-boundary-import, semantic-duplication).
Modular rule architecture
Rule logic is now organized in src/rules/ modules:
phase0-basic.ts— large-file, large-function, debug-leftover, dead-code, duplicate-function-name, any-abuse, catch-swallow, no-return-typephase1-complexity.ts— high-complexity, deep-nesting, too-many-params, high-coupling, promise-style-mix, magic-number, comment-contradictionphase2-crossfile.ts— unused-export, dead-file, unused-dependencyphase3-arch.ts— circular-dependency, layer-violation, cross-boundary-importphase5-ai.ts— hardcoded-config, inconsistent-error-handling, unnecessary-abstraction, naming-inconsistency, over-commentedphase8-semantic.ts— semantic-duplication
Bug fix: drift-ignore-file now works for cross-file rules
// drift-ignore-file now correctly suppresses issues from dead-file, unused-export, circular-dependency, and semantic-duplication phases.
Self-scan: 18/100 (LOW)
drift scans itself and scores 18/100.
VS Code Extension
eduardbar.vscode-drift v0.1.1 available in the Marketplace.
Install
npx @eduardbar/drift scan .v0.9.1
Fixed
drift trend:analyzeSingleCommitnow analyses the full project snapshot at each historical commit (viagit ls-tree+git show) instead of only the files in the diff. Score in eachTrendDataPointnow reflects total project health.drift trend: added uniform sampling (max 10 points per period) to prevent timeouts on large repos.drift trend/drift blame:DriftConfignow propagates through the full historical analysis call chain.
v0.9.0 — Historical drift analysis + HTML report + Badge + CI annotations
What's new
Phase 4 — Historical drift analysis
trend [period]command: analyzes debt evolution overweek,month,quarter,yearblame [target]command: shows which files/rules contribute most to driftTrendAnalyzerclass with linear regression, moving average, ASCII chartBlameAnalyzerclass with per-file and per-rule attribution viagit blame
Phase 6 — HTML report, badge, CI annotations
report [path]command: generates self-contained HTML report (dark mode, no external deps)badge [path]command: generatesbadge.svgin shields.io formatci [path]command: emits GitHub Actions workflow annotations + step summary
Fixes
- VERSION is now read dynamically from
package.json— never out of sync again - Added missing
program.parse()— commands were silently not executing
Install
npx @eduardbar/drift@0.9.0 scan .Usage
npx @eduardbar/drift scan . # scan for drift
npx @eduardbar/drift report . # generate HTML report
npx @eduardbar/drift badge . # generate badge.svg
npx @eduardbar/drift ci . --min-score 60 # CI gate
npx @eduardbar/drift trend month # trend last 30 days
npx @eduardbar/drift blame overall # who introduced most debt