Evidaxis

Ollama

repo
Inference & Serving · n = 14 · ollama/ollama
2 of 3 axes measurable · conf medium
convergence gate
Convergence gate: Gate: computed weekly across the cohort; no convergence event this week Development velocity: measured × Citation momentum: not measurable ∅ Direct-dependents momentum (deps.dev): measured ×
gate
0 of 3 axes

Gate: computed weekly across the cohort; no convergence event this week

Gate: computed weekly across the cohort; no convergence event this week
position in cohort distribution one of 14 in cohort
percentile 62 within cohort p25 p50 p75 p0 p100
percentile
p62
momentum averages present-axis z-scores; two- and three-axis scores are not strictly comparable
velocity z
velocity z gaugevelocity z+0.10 within cohort, log-slope +0.026/wk.0+0.10
velocity z
+0.10 σ
slope
+0.026/wk
log-slope +0.026/wk
citation z Citation source: not measured.
direct-dependents z
direct-dependents z gaugedirect-dependents z+0.07 within cohort, log-slope +0.011/point.0+0.07
direct-dependents z
+0.07 σ
slope
+0.011/point
Direct-dependents axis: measured.
cohort
14
systems measured
weekly commits
26.1
Development velocity axis: measured.
total citations
n/a
Citation source: not measured.
momentum
51.1
percentile p62
commit heatmap, last 26 weeks26.1/wk
weekly commits, 26 weeks26 weeks of commits, peak 47 in a week, 26 active weeks, 586 total.week 1: 16 commitsweek 2: 8 commitsweek 3: 9 commitsweek 4: 47 commitsweek 5: 14 commitsweek 6: 11 commitsweek 7: 20 commitsweek 8: 15 commitsweek 9: 14 commitsweek 10: 19 commitsweek 11: 31 commitsweek 12: 23 commitsweek 13: 16 commitsweek 14: 30 commitsweek 15: 24 commitsweek 16: 29 commitsweek 17: 26 commitsweek 18: 24 commitsweek 19: 33 commitsweek 20: 15 commitsweek 21: 20 commitsweek 22: 32 commitsweek 23: 45 commitsweek 24: 29 commitsweek 25: 16 commitsweek 26: 20 commits
weeks
26
peak/wk
47
active
26
total
586
citations by yearCitation source: not measured.
Daily dependents count (unscored) 1,871 dependents 1,101 direct, 787 indirect · pypi/ollama · deps.dev · the scored m5 axis uses weekly partitions

Ollama holds an Evidaxis momentum score of 51.1 of 100 on methodology m5, snapshot 2026-11-07, measured within the Inference & Serving cohort (n = 14). Axis coverage: 2 of 3 axes measurable. Gate: computed weekly across the cohort; no convergence event this week

Derived signals

second-order reads, computed from the published series

Three signals ship when the commit series is statistically sufficient; the rest are held in a reserved state until the data supports them. A reserved signal shows its reason, never a fabricated number. How these are computed.

recency-weighted swing trailing 13-week vs prior 39-week log-slope ratio -11.91, regime recent slope sign differs from prior window. prior slope +0.001, recent slope -0.014 per week. +0.001prior 39w-0.014recent 13w-11.91×
swing
-11.91×
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.012 with 95% CI -0.011 to +0.036, 50 degrees of freedom. CI spans zero.0+0.01295% CI -0.011, +0.036-0.011+0.036
sharpe
+0.012
95% ci
-0.011, +0.036
dof
50
snapshot 1 of 1 · · m5
commit changepoint52 weekly commit points. No significant changepoint detected (|delta slope| within the noise floor).no significant changepoint
changepoint
none detected
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
gate ETA reserved

reserved: needs snapshot history (1 snapshot exists)

status
reserved
value
insufficient history
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 1 of 1 · · m5

Reconstructed history

Ollama reconstructed weekly commits51 points, range 2 to 47 commits/wk.
min
2 commits/wk
max
47 commits/wk
latest
29 commits/wk
points
51

Weekly commits over the past year, reconstructed from git history (GitHub commit_activity). This is reconstructed, not a point-in-time capture. Evidaxis captures the Type-2 signals (watchers, issues, dependents) live and never backfills them; those are the moat.

Daily dependents count (unscored)

Ollama dependents over time19 points, range 1620 to 1871 dependents.
min
1620 dependents
max
1871 dependents
latest
1871 dependents
points
19

Downstream packages depending on pypi/ollama (deps.dev), captured point-in-time each snapshot. This daily series is unscored. The scored axis in m5 uses weekly partitions.

Measurement states

Ollama is under weekly measurement. History: 18 weekly observations; minimum 4. Development velocity axis: measured. Citation source: not measured. Direct-dependents axis: measured. Gate: computed weekly across the cohort; no convergence event this week

Sources

ollama/ollama development-velocity axis
ollama.com homepage

Direct-dependents momentum (deps.dev)

Direct-dependents axis: measured.

Coverage state
scored
Cohort z
+0.07
OLS slope
+0.011
Theil-Sen slope
+0.011
Latest direct dependents
1,114
Confirmed-clean points
29
Reconstructed history points
15
As-of partition
2026-10-19
Fragility veto
inactive
Rising vote
no

This axis measures the trajectory of a system's own packages: declared in its own tree, published under that name, and not attributed by deps.dev to another repository. A package with no repository link is unverified and stays. The self-name exclusion list is fixed at the v2h.1 panel. Systems with no admitted package are not measured on this axis. Points that cannot be derived exactly are withheld, and the series restarts after a withheld point.

The earliest weekly points of each series were read from deps.dev's BigQuery history on 2026-07-21; later points are weekly captures. m5 does not replay those partitions: each point is the stored system total, one package's unique_direct, or a complete sketch union, and a point that is not exact is withheld. Each record reports how many of its points are reconstructed history.

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

Axis definition · Snapshot axis correlations

entity_id e_TRJN6D7V12H methodology m5 snapshot 868e3c39d9c7 period 2026-w45 record JSON ↓ source snapshot

Score derived from public data on Evidaxis methodology m5, never edited by hand. Cite as: “Evidaxis, Ollama, entity e_TRJN6D7V12H, snapshot 2026-w45.”

Durable reference (format-independent): urn:evidaxis:claim:e_TRJN6D7V12H:m5:2026-11-07