Evidaxis
Dated record

graphify

repo · Graphify-Labs/graphify · paper: not linked · as of

Niche: not yet assigned.

117.7 commits per week averaged over the trailing window. No paper is linked in OpenAlex. deps.dev: 23 direct dependents. 143,580 GitHub stars, recorded, not scored. Measured for graphify as of 2026-11-07; sources: GitHub, OpenAlex and deps.dev where linked. Source definitions and captured readings accompany these measurements.

commits/wk 117.7 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 23 weekly axis input; partition 2026-11-07 measured · deps.dev snapshot ·
stars 143,580 recorded, not scored measured · GitHub ·
Download values (CSV) JSON record Follow this system (feed) Report an error

Is graphify still maintained?

117.7 commits per week averaged over the trailing window.

GitHub averaged 117.7 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: -58 · vs 26 weeks earlier: 18 · 52-week range: 0 to 176 commits in an individual week.

line chart: graphify, weekly commits, 118 in latest week, 2025-11-09 to 2026-11-01
graphify averaged 117.7 commits a week. GitHub commit_activity · .
Latest eight weeks
Week startingCommits
2026-09-13107
2026-09-20126
2026-09-27118
2026-10-04176
2026-10-11152
2026-10-18139
2026-10-25160
2026-11-01118
heatmap chart: graphify, weeks with commits, 26 of 26, 2026-05-10 to 2026-11-01
26 of the last 26 captured weeks had commits for graphify. 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-150
2026-02-220
2026-03-010
2026-03-080
2026-03-150
2026-03-220
2026-03-2910
2026-04-05120
2026-04-1239
2026-04-1937
2026-04-2674
2026-05-03100
2026-05-1069
2026-05-1745
2026-05-2459
2026-05-3167
2026-06-0767
2026-06-1441
2026-06-2163
2026-06-28128
2026-07-0594
2026-07-12106
2026-07-1990
2026-07-2672
2026-08-0215
2026-08-0992
2026-08-1687
2026-08-2376
2026-08-3058
2026-09-0695
2026-09-13107
2026-09-20126
2026-09-27118
2026-10-04176
2026-10-11152
2026-10-18139
2026-10-25160
2026-11-01118

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 week117.725860 to 117.7GitHub, trailing 12 weeks2026-11-07Public query109.7
Citing worksno readingno readingno readingno readingOpenAlex, all years2026-11-07Public queryno reading
Weekly direct dependents23no readingno reading23 to 23Weekly direct dependents2026-11-07Public queryno reading
Daily package dependents (unscored)no readingno readingno readingno readingdeps.dev REST, unscorednot capturedPublic queryno reading
Stars143,58017,881no reading104,117 to 143,580GitHub stars, unscored2026-11-07Public query139,517

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

How to cite graphify's record?

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

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

Is anyone using graphify?

deps.dev: 23 direct dependents.

Weekly dependents
PartitionDirect dependentsWeekly pointsMethod
no partition231m5 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): no reading; captured not captured; package: not captured. 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. 143,580 GitHub stars, recorded, not scored.

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

What changed since the last snapshot?

3 published readings changed between snapshots d1eb0cec0f6a and 868e3c39d9c7.

slope chart: graphify, changed published values, 2, 2026-10-31 to 2026-11-07
2 published values changed for graphify since 2026-10-31. Evidaxis snapshots · .
Snapshot values
MetricPreviousCurrentDelta
Commits per week109.7117.78
Citing worksno readingno readingno reading
Weekly direct dependentsno reading23no reading
Stars139,517143,5804,063

Evidaxis snapshots · period 2026-10-31 to 2026-11-07 · n = 14 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 graphify, and why

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

Unmeasured slots
ReadingReason
Citing worksnot linked
Daily package dependents (unscored)no reading captured

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: 14 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

graphify

repo
Unassigned (AI-v1 census) · n = 6545 · Graphify-Labs/graphify
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 83 within cohort p25 p50 p75 p0 p100
percentile
p83
· 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+2.22 within cohort, log-slope +0.038/wk.0+2.22
velocity z
+2.22 σ
slope
+0.038/wk
· Evidaxis snapshot · 2026-11-07
log-slope +0.038/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
117.7
Development velocity axis: measured.
total citations
no reading
Citation source: not measured.
momentum
77.8
percentile p83
commit heatmap, last 26 weeks117.7/wk
weekly commits, 26 weeks26 weeks of commits, peak 176 in a week, 26 active weeks, 2420 total.week 1: 69 commitsweek 2: 45 commitsweek 3: 59 commitsweek 4: 67 commitsweek 5: 67 commitsweek 6: 41 commitsweek 7: 63 commitsweek 8: 128 commitsweek 9: 94 commitsweek 10: 106 commitsweek 11: 90 commitsweek 12: 72 commitsweek 13: 15 commitsweek 14: 92 commitsweek 15: 87 commitsweek 16: 76 commitsweek 17: 58 commitsweek 18: 95 commitsweek 19: 107 commitsweek 20: 126 commitsweek 21: 118 commitsweek 22: 176 commitsweek 23: 152 commitsweek 24: 139 commitsweek 25: 160 commitsweek 26: 118 commits
weeks
26
peak/wk
176
active
26
total
2420
· Evidaxis snapshot · 2026-11-07
citations by yearCitation source: not measured.
recency-weighted swing trailing 13-week vs prior 39-week log-slope ratio +0.38, regime recent slope below prior window. prior slope +0.160, recent slope +0.061 per week. +0.160prior 39w+0.061recent 13w+0.38×
swing
+0.38×
regime
recent slope below prior window
windows
13w vs 39w
snapshot 1 of 1 · · m5
commit-axis Sharpe log-linear slope over residual std, value +0.123 with 95% CI +0.069 to +0.176, 50 degrees of freedom. CI excludes zero.0+0.12395% CI +0.069, +0.176+0.069+0.176
sharpe
+0.123
95% ci
+0.069, +0.176
dof
50
snapshot 1 of 1 · · m5
commit changepoint52 weekly commit points. Changepoint at week 48 (2026-10-10), slope change -13.512 commits per week.2026-10-10
date
week
48 of 52
Δslope
-13.512/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 14 of 14 · · 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
23
Confirmed-clean points
1
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

Reconstructed history

Reconstructed from git history, not a point-in-time capture. This series is separate from captured observations.

sparkline chart: graphify, reconstructed commits, 13, 2026-w13 to 2026-w38
graphify recorded 13 reconstructed commits. Git history reconstruction · .
Reconstructed weekly commits
PeriodCommits
2026-w1310
2026-w14120
2026-w1539
2026-w1637
2026-w1774
2026-w18100
2026-w1969
2026-w2045
2026-w2159
2026-w2267
2026-w2367
2026-w2441
2026-w2563
2026-w26128
2026-w2794
2026-w28106
2026-w2989
2026-w3072
2026-w3115
2026-w3292
2026-w3387
2026-w3473
2026-w3555
2026-w3678
2026-w37105
2026-w3813

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