Affected areas: ⚙️ CI / Build 📦 Dependencies 📝 Version Control
Based on 20 prior commits
7 connected
We've detected 6 changes that differ from your project's normal patterns. Each change shows what typically happens versus what we observed this time.
815ce2f4 Adding travis-ciwhen CI builds and code changes happen together, change focus and build time tend to move together.
Development pattern shift detected in Version Control.\n\nSIGNAL: Change Locality is 333.4x below the typical baseline (observed: 0.0000, typical: 1.00).\nTRIGGER COMMIT: 815ce2f4 — Adding travis-ci\n\nFILES CHANGED IN TRIGGER (1):\n - .travis.yml\n\nRECENT COMMITS (19 total, showing top 5):\n aa9a7870 — Adding MFA support (4 files)\n c3ae6e02 — Auto turn form into HTML (2 files)\n c93b3285 — Sending back full body on mfa, not just message (2 files)\n 4e2bd31f — adding /connect/get to module (3 files)\n 204acb11 — start tests (5 files)\n ... and 14 more commits\n\nCORRELATED PATTERNS:\n [CRITICAL] when CI builds and code changes happen together, change focus and build time tend to move together.\n → Profile the build pipeline to identify bottlenecks. Check for newly added expensive tests or build steps.\n → Review whether these cross-cutting changes have adequate test coverage.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit 815ce2f4 — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.
50f1d9bd OpenAPI generated code at 02_17_21_15_15_59 (#408)when CI builds and code changes happen together, file count and build time tend to move together.
when code changes occur, file count tends to increase.
Development pattern shift detected in Version Control.\n\nSIGNAL: Files Changed is 64.8x above the typical baseline (observed: 49, typical: 1.00).\nTRIGGER COMMIT: 50f1d9bd — OpenAPI generated code at 02_17_21_15_15_59 (#408)\n\nFILES CHANGED IN TRIGGER (49):\n - .circleci/config.yml\n - .dockerignore\n - .editorconfig\n - .env.example\n - .gitignore\n - .nvmrc\n - .openapi-generator-ignore\n - .prettierrc\n - CHANGELOG.md\n - CONTRIBUTING.md\n - Dockerfile\n - Makefile\n - PUBLISH.md\n - README.md\n - index.d.ts\n ... and 34 more\n\nRECENT COMMITS (20 total, showing top 5):\n aa9a7870 — Adding MFA support (4 files)\n 815ce2f4 — Adding travis-ci (1 files)\n c3ae6e02 — Auto turn form into HTML (2 files)\n c93b3285 — Sending back full body on mfa, not just message (2 files)\n 4e2bd31f — adding /connect/get to module (3 files)\n ... and 15 more commits\n\nCORRELATED PATTERNS:\n [CRITICAL] when CI builds and code changes happen together, file count and build time tend to move together.\n → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n [WATCH] when code changes occur, file count tends to increase.\n → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit 50f1d9bd — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.
aa9a7870 Adding MFA supportwhen dependency changes and code changes happen together, code spread tends to move together.
when code changes occur, code spread tends to increase.
Development pattern shift detected in Version Control.\n\nSIGNAL: Change Dispersion is 52.6x above the typical baseline (observed: 1.50, typical: 0.0190).\nTRIGGER COMMIT: aa9a7870 — Adding MFA support\n\nFILES CHANGED IN TRIGGER (4):\n - .gitignore\n - lib/client.js\n - lib/defaults.js\n - package.json\n\nRECENT COMMITS (19 total, showing top 5):\n 815ce2f4 — Adding travis-ci (1 files)\n c3ae6e02 — Auto turn form into HTML (2 files)\n c93b3285 — Sending back full body on mfa, not just message (2 files)\n 4e2bd31f — adding /connect/get to module (3 files)\n 204acb11 — start tests (5 files)\n ... and 14 more commits\n\nCORRELATED PATTERNS:\n [CONCERN] when dependency changes and code changes happen together, code spread tends to move together.\n → Review recent PRs for scope creep. Consider breaking large changes into focused commits.\n [WATCH] when code changes occur, code spread tends to increase.\n → Review recent PRs for scope creep. Consider breaking large changes into focused commits.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit aa9a7870 — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.
The dispersion for this change was 1.50. Historically, similar changes had a value of 0.0190 ± 0.0190.
9c4d6418 when dependency changes and code changes happen together, novelty of file pairings and dependency count tend to move together.
when CI builds and dependency changes happen together, dependency count and build time tend to move in opposite directions.
when dependency changes occur, dependency count tends to increase.
Development pattern shift detected in Dependencies.\n\nSIGNAL: Total Dependencies is 34.4x below the typical baseline (observed: 167, typical: 218.0).\nTRIGGER COMMIT: 9c4d6418 — \n\nRECENT COMMITS (20 total, showing top 5):\n aa9a7870 — Adding MFA support (4 files)\n 815ce2f4 — Adding travis-ci (1 files)\n c3ae6e02 — Auto turn form into HTML (2 files)\n c93b3285 — Sending back full body on mfa, not just message (2 files)\n 4e2bd31f — adding /connect/get to module (3 files)\n ... and 15 more commits\n\nCORRELATED PATTERNS:\n [CRITICAL] when dependency changes and code changes happen together, novelty of file pairings and dependency count tend to move together.\n → Investigate which files are being combined unexpectedly. Prioritize testing these changes.\n [WATCH] when dependency changes occur, dependency count tends to increase.\n → Audit new dependencies for necessity, maintenance status, and known vulnerabilities.\n [INFO] when CI builds and dependency changes happen together, dependency count and build time tend to move in opposite directions.\n → Confirm test coverage hasn't decreased alongside faster builds.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit 9c4d6418 — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.
The dependency count for this change was 167. Historically, similar changes had a value of 218.0 ± 1.00.
b0fed4aa OpenAPI generated code at 2022-10-25T20:06:45Zwhen CI builds and code changes happen together, novelty of file pairings and build time tend to move together.
when dependency changes and code changes happen together, novelty of file pairings and dependency count tend to move together.
when code changes occur, novelty of file pairings tends to decrease.
Development pattern shift detected in Version Control.\n\nSIGNAL: Co-change Novelty is 29.8x above the typical baseline (observed: 0.1053, typical: 0.0000).\nTRIGGER COMMIT: b0fed4aa — OpenAPI generated code at 2022-10-25T20:06:45Z\n\nFILES CHANGED IN TRIGGER (19):\n - CHANGELOG.md\n - api.ts\n - base.ts\n - common.ts\n - configuration.ts\n - dist/api.d.ts\n - dist/api.js\n - dist/base.d.ts\n - dist/base.js\n - dist/common.d.ts\n - dist/common.js\n - dist/configuration.d.ts\n - dist/configuration.js\n - dist/index.d.ts\n - dist/index.js\n ... and 4 more\n\nRECENT COMMITS (20 total, showing top 5):\n aa9a7870 — Adding MFA support (4 files)\n 815ce2f4 — Adding travis-ci (1 files)\n c3ae6e02 — Auto turn form into HTML (2 files)\n c93b3285 — Sending back full body on mfa, not just message (2 files)\n 4e2bd31f — adding /connect/get to module (3 files)\n ... and 15 more commits\n\nCORRELATED PATTERNS:\n [CRITICAL] when CI builds and code changes happen together, novelty of file pairings and build time tend to move together.\n → Investigate which files are being combined unexpectedly. Prioritize testing these changes.\n [CRITICAL] when dependency changes and code changes happen together, novelty of file pairings and dependency count tend to move together.\n → Investigate which files are being combined unexpectedly. Prioritize testing these changes.\n [INFO] when code changes occur, novelty of file pairings tends to decrease.\n → Review whether recent commits are routine maintenance or a sign of narrow, repetitive modifications that lack expected variety.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit b0fed4aa — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.
c506643e when CI builds and code changes happen together, change focus and build time tend to move together.
when CI builds and code changes happen together, file count and build time tend to move together.
when CI builds and code changes happen together, novelty of file pairings and build time tend to move together.
when CI builds and dependency changes happen together, dependency count and build time tend to move in opposite directions.
Development pattern shift detected in CI / Build.\n\nSIGNAL: Build Duration is 3.2x above the typical baseline (observed: 67.00, typical: 48.00).\nTRIGGER COMMIT: c506643e — \n\nRECENT COMMITS (20 total, showing top 5):\n aa9a7870 — Adding MFA support (4 files)\n 815ce2f4 — Adding travis-ci (1 files)\n c3ae6e02 — Auto turn form into HTML (2 files)\n c93b3285 — Sending back full body on mfa, not just message (2 files)\n 4e2bd31f — adding /connect/get to module (3 files)\n ... and 15 more commits\n\nCORRELATED PATTERNS:\n [CRITICAL] when CI builds and code changes happen together, change focus and build time tend to move together.\n → Profile the build pipeline to identify bottlenecks. Check for newly added expensive tests or build steps.\n → Review whether these cross-cutting changes have adequate test coverage.\n [CRITICAL] when CI builds and code changes happen together, file count and build time tend to move together.\n → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n [CRITICAL] when CI builds and code changes happen together, novelty of file pairings and build time tend to move together.\n → Investigate which files are being combined unexpectedly. Prioritize testing these changes.\n [INFO] when CI builds and dependency changes happen together, dependency count and build time tend to move in opposite directions.\n → Confirm test coverage hasn't decreased alongside faster builds.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit c506643e — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.
The run duration for this change was 67.00. Historically, similar changes had a value of 48.00 ± 4.00.
Development drift analysis for plaid/plaid-node (Mar 26, 2013 at 04:14 AM to Mar 05, 2026 at 09:02 PM).
DEVIATIONS FROM BASELINE:
- Version Control / Change Locality: 0.0000 (typical: 1.00, 333.4x below)
- Version Control / Files Changed: 49 (typical: 1.00, 64.8x above)
- Version Control / Change Dispersion: 1.50 (typical: 0.0190, 52.6x above)
- Dependencies / Total Dependencies: 167 (typical: 218.0, 34.4x below)
- Version Control / Co-change Novelty: 0.1053 (typical: 0.0000, 29.8x above)
- CI / Build / Build Duration: 67.00 (typical: 48.00, 3.2x above)
RISK PATTERNS (actionable only):
- [Action Required] 3 patterns:
* when CI builds and code changes happen together, novelty of file pairings and build time tend to move together.
* when CI builds and code changes happen together, novelty of file pairings tends to move together.
* when dependency changes and code changes happen together, novelty of file pairings and dependency count tend to move together.
Impact: Files that don't normally change together are being modified in the same commits. This indicates novel, untested interactions that may introduce bugs. Escalated from Needs Attention — multiple correlated patterns converge on the same signal families.
Action: Investigate which files are being combined unexpectedly. Prioritize testing these changes.
- [Action Required] when CI builds and code changes happen together, change focus and build time tend to move together.
(2 independent confirmations)
Impact: Builds are taking longer. Slower CI feedback loops reduce developer productivity and delay catching issues. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.
Action: Profile the build pipeline to identify bottlenecks. Check for newly added expensive tests or build steps.
- [Action Required] 2 patterns:
* when CI builds and code changes happen together, file count and build time tend to move together.
* when CI builds and code changes happen together, file count tends to move together.
Impact: Commits are touching more files than usual, increasing review burden and risk of regressions. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.
Action: Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.
- [Action Required] 2 patterns:
* when CI builds and code changes happen together, code spread and build time tend to move together.
* when CI builds and code changes happen together, code spread tends to move together.
Impact: Changes are spreading across unrelated parts of the codebase. This makes reviews harder and increases the chance of unexpected side effects. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.
Action: Review recent PRs for scope creep. Consider breaking large changes into focused commits.
- [Action Required] when CI builds and code changes happen together, change focus tends to move in opposite directions.
Impact: Changes span files that don't normally change together, suggesting cross-cutting concerns that may be harder to test. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.
Action: Review whether these cross-cutting changes have adequate test coverage.
- [Needs Attention] when code changes occur, novelty of file pairings tends to increase.
Impact: Files that don't normally change together are being modified in the same commits. This indicates novel, untested interactions that may introduce bugs.
Action: Investigate which files are being combined unexpectedly. Prioritize testing these changes.
- [Needs Attention] when dependency changes and code changes happen together, change focus tends to move in opposite directions.
Impact: Changes span files that don't normally change together, suggesting cross-cutting concerns that may be harder to test. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.
Action: Review whether these cross-cutting changes have adequate test coverage.
- [Needs Attention] when dependency changes and code changes happen together, code spread tends to move together.
Impact: Changes are spreading across unrelated parts of the codebase. This makes reviews harder and increases the chance of unexpected side effects. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.
Action: Review recent PRs for scope creep. Consider breaking large changes into focused commits.
- [Worth Monitoring] when dependency changes occur, dependency count tends to increase.
(2 independent confirmations)
Impact: The dependency count is growing, expanding the supply-chain attack surface and potential for version conflicts.
Action: Audit new dependencies for necessity, maintenance status, and known vulnerabilities.
- [Worth Monitoring] when code changes occur, code spread tends to increase.
(2 independent confirmations)
Impact: Changes are spreading across unrelated parts of the codebase. This makes reviews harder and increases the chance of unexpected side effects.
Action: Review recent PRs for scope creep. Consider breaking large changes into focused commits.
- [Worth Monitoring] when code changes occur, file count tends to increase.
(3 independent confirmations)
Impact: Commits are touching more files than usual, increasing review burden and risk of regressions.
Action: Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.
COMMITS (20):
aa9a7870 — Adding MFA support (4 files)
815ce2f4 — Adding travis-ci (1 files)
c3ae6e02 — Auto turn form into HTML (2 files)
c93b3285 — Sending back full body on mfa, not just message (2 files)
4e2bd31f — adding /connect/get to module (3 files)
204acb11 — start tests (5 files)
24eca04b — remove a user (4 files)
11c639df — make step connect working and tested (3 files)
4bd11954 — fix mfa returned value (3 files)
68d39781 — Merge pull request #1 from Philmod/master (9 files)
... and 10 more
SOURCE FILES CHANGED (46):
- .gitignore (modified)
- lib/client.js (modified)
- lib/defaults.js (modified)
- package.json (modified)
- .travis.yml (modified)
- npm-debug.log (modified)
- Makefile (modified)
- README.md (modified)
- test/client.js (modified)
- test/utils.js (modified)
- LICENSE (modified)
- .jshintrc (modified)
- lib/index.js (modified)
- .npmignore (modified)
- circle.yml (modified)
- .jscsrc (modified)
- index.js (modified)
- test/authenticated.js (modified)
- test/public.js (modified)
- lib/PlaidClient.js (modified)
... and 26 more
TASKS:
1. ROOT CAUSE: For each deviation, identify the commit(s) that caused it.
Focus on [Action Required] and [Needs Attention] items first.
2. FIXES: Provide concrete fixes with file paths and code changes.
Goal: bring metrics back toward baseline without disrupting velocity.
3. PRIORITY: Rank fixes by urgency (immediate vs. next sprint).
4. AFTER FIXING: Run `evo analyze . --verify` to confirm deviations decreased.
If a change was intentional, accept it: `evo accept . <N>`.
5. FINDING SUMMARIES: At the end, include a section like this:
## Finding Summaries
- [family/metric]: One plain-English sentence for a non-technical reader.
(This lets the user run `evo enrich . --from response.txt` to store friendly descriptions.)
Evolution Engine has 44 universal patterns learned from 200+ open-source repositories. The more signal families you connect, the more cross-family patterns can be detected.
Enable these adapters to unlock additional signal families and cross-family pattern detection.
SENTRY_AUTH_TOKEN Setup guide →export GITHUB_TOKEN=$(gh auth token)pytest --junitxml=junit.xml or pytest --cov --cov-report=xmlevo analyze . — new adapters are detected automaticallyevo sources to confirm which adapters are active