Evidaxis
Dated record

OmniRoute

repo · OmniRoute · paper: not linked · as of

Niche: not yet assigned.

497.5 commits per week averaged over the trailing window. No paper is linked in OpenAlex. Dependents: no reading captured in the partition. 85,204 GitHub stars, recorded, not scored. Measured for OmniRoute as of 2026-11-07; sources: GitHub, OpenAlex and deps.dev where linked.

commits/wk 497.5 averaged, trailing window last commit week 2026-11-01 measured · GitHub ·
citations no paper linked all years, indexed to date no reading · OpenAlex ·
direct dependents not captured this week weekly axis input; partition 2026-11-07 no reading · deps.dev snapshot ·
stars 85,204 recorded, not scored measured · GitHub ·
Download values (CSV) JSON record Follow this system (feed) Report an error

Is OmniRoute still maintained?

497.5 commits per week averaged over the trailing window.

GitHub averaged 497.5 per week over the trailing window; raw weekly counts below are individual weeks.

Last commit week 2026-11-01.

Commits in the latest captured week vs 4 weeks earlier: -173 · vs 26 weeks earlier: 237 · 52-week range: 0 to 1,176 commits in an individual week.

line chart: OmniRoute, weekly commits, 428 in latest week, 2025-11-09 to 2026-11-01
OmniRoute averaged 497.5 commits a week. GitHub commit_activity · .
Latest eight weeks
Week startingCommits
2026-09-13610
2026-09-20385
2026-09-27356
2026-10-04601
2026-10-11518
2026-10-18753
2026-10-25468
2026-11-01428
heatmap chart: OmniRoute, weeks with commits, 26 of 26, 2026-05-10 to 2026-11-01
26 of the last 26 captured weeks had commits for OmniRoute. GitHub commit_activity · .
All 52 weeks
Weekly commits
Week startingCommits
2025-11-090
2025-11-160
2025-11-230
2025-11-300
2025-12-070
2025-12-140
2025-12-210
2025-12-280
2026-01-040
2026-01-110
2026-01-180
2026-01-250
2026-02-010
2026-02-080
2026-02-1556
2026-02-22167
2026-03-01163
2026-03-08196
2026-03-15254
2026-03-22304
2026-03-29547
2026-04-05148
2026-04-12183
2026-04-19165
2026-04-26351
2026-05-03191
2026-05-10561
2026-05-17260
2026-05-24762
2026-05-31390
2026-06-07167
2026-06-14100
2026-06-2150
2026-06-28113
2026-07-05442
2026-07-12584
2026-07-191,176
2026-07-26379
2026-08-02477
2026-08-09792
2026-08-16694
2026-08-23567
2026-08-30394
2026-09-06196
2026-09-13610
2026-09-20385
2026-09-27356
2026-10-04601
2026-10-11518
2026-10-18753
2026-10-25468
2026-11-01428

GitHub commit_activity · period 2025-11-09 to 2026-11-01 · n = 52 weeks · method weekly totals; reconstructed dates · updated · version 868e3c39d9c7-b1 · CSV

Readings

Recorded values and sources
ReadingValueΔ 4 weeksΔ 26 weeks52-week rangeInstrumentDateReproducePrevious reading
Commits per week497.5-54.7270.40 to 558GitHub, trailing 12 weeks2026-11-07Public query518.8
Citing worksno readingno readingno readingno readingOpenAlex, all years2026-11-07Public queryno reading
Weekly direct dependentsno readingno readingno readingno readingWeekly direct dependents2026-11-07Public queryno reading
Daily package dependents (unscored)0no readingno reading0 to 0deps.dev REST, unscored2026-11-05Public query0
Stars85,2049,715no reading70,466 to 85,204GitHub stars, unscored2026-11-07Public query82,913

Evidaxis snapshot · period 2026-11-07 · n = 1 system · method source linked readings · updated · version 868e3c39d9c7-b1

How to cite OmniRoute's record?

Evidaxis. OmniRoute measurement record. Snapshot 2026-11-07. urn:evidaxis:claim:e_S4RT1S1K6BE:m5:2026-11-07. CC0-1.0. https://evidaxis.org/e/e_S4RT1S1K6BE/

Evidaxis · period 2026-11-07 · n = 1 system · method claim URN · updated · version 868e3c39d9c7-b1

Is anyone using OmniRoute?

Dependents: no reading captured in the partition.

Weekly dependents
PartitionDirect dependentsWeekly pointsMethod
no partitionno reading0m5 own packages

deps.dev weekly direct dependents of the system's own packages. A package counts when it is declared in the system's own tree, published under that name and not attributed by deps.dev to another repository. Partition dates can repeat across snapshots. Package linkage is not uniformly verified: packages with no repository metadata (no_link) are unverified and remain admitted.

Daily package dependents (unscored): 0; captured 2026-11-05; package: npm/omniroute. deps.dev REST count for one identity-verified pinned package, captured daily and never scored. Its package scope differs from the weekly package union; neither value replaces the other. 85,204 GitHub stars, recorded, not scored.

sparkline chart: OmniRoute, daily dependents, 0, 2026-w39 to 2026-w45
OmniRoute recorded 0 daily dependents. deps.dev REST (unscored) · .
Captured daily series
Unscored daily dependents, as captured
PeriodDependents
2026-w390
2026-w400
2026-w410
2026-w420
2026-w430
2026-w440
2026-w450

deps.dev · period 2026-11-07 · n = 0 partitions · method m5 own packages · updated · version 868e3c39d9c7-b1 · CSV

What changed since the last snapshot?

2 published readings changed between snapshots d1eb0cec0f6a and 868e3c39d9c7.

slope chart: OmniRoute, changed published values, 2, 2026-10-31 to 2026-11-07
2 published values changed for OmniRoute since 2026-10-31. Evidaxis snapshots · .
Snapshot values
MetricPreviousCurrentDelta
Commits per week518.8497.5-21.3
Citing worksno readingno readingno reading
Weekly direct dependentsno readingno readingno reading
Stars82,91385,2042,291

Evidaxis snapshots · period 2026-10-31 to 2026-11-07 · n = 7 partitions · method paired snapshot values · updated · version 868e3c39d9c7-b1 · History CSV

Take the data or follow changes

Values and captured history are available under CC0-1.0. The system feed records changes to published numbers.

Values CSVHistory CSVJSON recordAtom feedJSON FeedAdd Evidaxis as a preferred source on GoogleReport an error

Evidaxis · period 2026-11-07 · n = 1 system · method CC0-1.0 open export · updated · version 868e3c39d9c7-b1

For teams tracking many systems

Use the cohort CSV, snapshot archive and membership manifest to reproduce observations across systems.

Cohort CSV · Snapshot archive · Membership manifest

Paper and links

Source records identify the system, repository and linked works; no paper authors are published.

    What is not measured for OmniRoute, and why

    Missing readings describe instrument coverage. A missing value is not a measured zero.

    Unmeasured slots
    ReadingReason
    Citing worksnot linked
    Weekly direct dependentsno partition

    Dependents: no reading captured in the partition.

    Gate ETA: never published; Evidaxis makes no public actionable prediction.

    Dependents ecosystem composition: no reading; this field is not present in the snapshot.

    Evidaxis · period 2026-11-07 · n = 1 system · method measurement coverage · updated · version 868e3c39d9c7-b1

    Measurement detail

    Gate, gauges, percentile, derived signals and snapshot receipt

    History: 7 weekly observations; minimum 4. Axis coverage: 1 of 3 axes measurable. Gate: not computable - 1 of 3 axes measurable

    Gate: not computable - 1 of 3 axes measurable

    OmniRoute

    repo
    Unassigned (AI-v1 census) · n = 6545 · OmniRoute
    1 of 3 axes measurable · conf low
    convergence gate
    Convergence gate: Gate: not computable - 1 of 3 axes measurable Development velocity: rising vote Citation momentum: not measurable ∅ Direct-dependents momentum (deps.dev): not measurable ∅
    gate
    1 of 3 axes

    Gate: not computable - 1 of 3 axes measurable

    · Evidaxis snapshot · 2026-11-07
    Gate: not computable - 1 of 3 axes measurable
    position in cohort distribution one of 6545 in cohort
    percentile 80 within cohort p25 p50 p75 p0 p100
    percentile
    p80
    · Evidaxis snapshot · 2026-11-07
    momentum averages present-axis z-scores; two- and three-axis scores are not strictly comparable
    velocity z
    velocity z gaugevelocity z+1.66 within cohort, log-slope +0.029/wk.0+1.66
    velocity z
    +1.66 σ
    slope
    +0.029/wk
    · Evidaxis snapshot · 2026-11-07
    log-slope +0.029/wk
    citation z Citation source: not measured.
    direct-dependents z Direct-dependents axis: minimum of 14 usable points of the new quantity and 5 latest dependents not met.
    cohort
    6545
    systems measured
    weekly commits
    497.5
    Development velocity axis: measured.
    total citations
    no reading
    Citation source: not measured.
    momentum
    70.7
    percentile p80
    commit heatmap, last 26 weeks497.5/wk
    weekly commits, 26 weeks26 weeks of commits, peak 1176 in a week, 26 active weeks, 12223 total.week 1: 561 commitsweek 2: 260 commitsweek 3: 762 commitsweek 4: 390 commitsweek 5: 167 commitsweek 6: 100 commitsweek 7: 50 commitsweek 8: 113 commitsweek 9: 442 commitsweek 10: 584 commitsweek 11: 1176 commitsweek 12: 379 commitsweek 13: 477 commitsweek 14: 792 commitsweek 15: 694 commitsweek 16: 567 commitsweek 17: 394 commitsweek 18: 196 commitsweek 19: 610 commitsweek 20: 385 commitsweek 21: 356 commitsweek 22: 601 commitsweek 23: 518 commitsweek 24: 753 commitsweek 25: 468 commitsweek 26: 428 commits
    weeks
    26
    peak/wk
    1176
    active
    26
    total
    12223
    · Evidaxis snapshot · 2026-11-07
    citations by yearCitation source: not measured.
    Daily dependents count (unscored) 0 dependents 0 direct · npm/omniroute · deps.dev · the scored m5 axis uses weekly partitions
    recency-weighted swing trailing 13-week vs prior 39-week log-slope ratio -0.05, regime recent slope sign differs from prior window. prior slope +0.206, recent slope -0.011 per week. +0.206prior 39w-0.011recent 13w-0.05×
    swing
    -0.05×
    regime
    recent slope sign differs from prior window
    windows
    13w vs 39w
    snapshot 1 of 1 · · m5
    commit-axis Sharpe log-linear slope over residual std, value +0.095 with 95% CI +0.032 to +0.157, 50 degrees of freedom. CI excludes zero.0+0.09595% CI +0.032, +0.157+0.032+0.157
    sharpe
    +0.095
    95% ci
    +0.032, +0.157
    dof
    50
    snapshot 1 of 1 · · m5
    commit changepoint52 weekly commit points. Changepoint at week 50 (2026-10-24), slope change -176.136 commits per week.2026-10-24
    date
    week
    50 of 52
    Δslope
    -176.136/wk
    snapshot 1 of 1 · · m5
    code-leads-citation lag reserved

    reserved: citation series too short / axis absent for cross-correlation

    status
    reserved
    value
    insufficient data
    snapshot 1 of 1 · · m5
    axis alpha vs cohort reserved

    reserved: cohort N too small for regression (power ~0)

    status
    reserved
    value
    insufficient data
    snapshot 1 of 1 · · m5
    methodology gate snapshot 1 of 1 · · m5
    commit weeks
    52
    citation years
    0
    shipped
    3
    reserved
    3

    shipped

    • recency-swing
    • commit-sharpe
    • commit-changepoint

    reserved

    • code-leads-citation-lag
    • axis-alpha
    • gate-eta
    snapshot 7 of 7 · · m5

    Direct-dependents momentum (deps.dev)

    Direct-dependents axis: minimum of 14 usable points of the new quantity and 5 latest dependents not met.

    Coverage state
    below_floor
    Cohort z
    no axis
    OLS slope
    no reading
    Theil-Sen slope
    no reading
    Latest direct dependents
    no reading
    Confirmed-clean points
    0
    Reconstructed history points
    no reading
    As-of partition
    no reading
    Fragility veto
    no reading
    Rising vote
    no

    Source: deps.dev (Google), CC-BY 4.0. Modified: aggregated to system-level counts and momentum scores.

    Axis definition · Snapshot axis correlations

    Evidaxis · period 2026-11-07 · n = 1 system · method measurement detail · updated · version 868e3c39d9c7-b1 · record JSON · snapshot receipt