Evidaxis
Dated record

tensorflow-federated

repo · google-parfait/tensorflow-federated · paper: not linked · as of

Niche: not yet assigned.

2.2 commits per week averaged over the trailing window. No paper is linked in OpenAlex. deps.dev: 1 direct dependents, below the 5-dependent floor. 2,453 GitHub stars, recorded, not scored. Measured for tensorflow-federated as of 2026-11-07; sources: GitHub, OpenAlex and deps.dev where linked.

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

Is tensorflow-federated still maintained?

2.2 commits per week averaged over the trailing window.

GitHub averaged 2.2 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: -1 · vs 26 weeks earlier: -1 · 52-week range: 0 to 9 commits in an individual week.

line chart: tensorflow-federated, weekly commits, 1 in latest week, 2025-11-09 to 2026-11-01
tensorflow-federated averaged 2.2 commits a week. GitHub commit_activity · .
Latest eight weeks
Week startingCommits
2026-09-132
2026-09-200
2026-09-271
2026-10-042
2026-10-110
2026-10-187
2026-10-254
2026-11-011
heatmap chart: tensorflow-federated, weeks with commits, 19 of 26, 2026-05-10 to 2026-11-01
19 of the last 26 captured weeks had commits for tensorflow-federated. GitHub commit_activity · .
All 52 weeks
Weekly commits
Week startingCommits
2025-11-093
2025-11-161
2025-11-230
2025-11-302
2025-12-071
2025-12-140
2025-12-211
2025-12-280
2026-01-042
2026-01-110
2026-01-181
2026-01-251
2026-02-012
2026-02-084
2026-02-150
2026-02-222
2026-03-013
2026-03-082
2026-03-159
2026-03-221
2026-03-291
2026-04-051
2026-04-120
2026-04-193
2026-04-260
2026-05-032
2026-05-106
2026-05-172
2026-05-240
2026-05-312
2026-06-071
2026-06-141
2026-06-212
2026-06-280
2026-07-052
2026-07-121
2026-07-192
2026-07-260
2026-08-021
2026-08-090
2026-08-161
2026-08-230
2026-08-305
2026-09-064
2026-09-132
2026-09-200
2026-09-271
2026-10-042
2026-10-110
2026-10-187
2026-10-254
2026-11-011

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 week2.20.70.20.9 to 2.5GitHub, trailing 12 weeks2026-11-07Public query2.2
Citing worksno readingno readingno readingno readingOpenAlex, all years2026-11-07Public queryno reading
Weekly direct dependents1no readingno reading1 to 1Weekly direct dependents2026-11-07Public queryno reading
Daily package dependents (unscored)3no readingno reading3 to 3deps.dev REST, unscored2026-11-06Public query3
Stars2,453-1no reading2,452 to 2,454GitHub stars, unscored2026-11-07Public query2,453

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

How to cite tensorflow-federated's record?

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

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

Is anyone using tensorflow-federated?

deps.dev: 1 direct dependents, below the 5-dependent floor.

Weekly dependents
PartitionDirect dependentsWeekly pointsMethod
no partition11m5 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): 3; captured 2026-11-06; package: pypi/tensorflow-federated. 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. 2,453 GitHub stars, recorded, not scored.

sparkline chart: tensorflow-federated, daily dependents, 3, 2026-w39 to 2026-w45
tensorflow-federated recorded 3 daily dependents. deps.dev REST (unscored) · .
Captured daily series
Unscored daily dependents, as captured
PeriodDependents
2026-w393
2026-w403
2026-w413
2026-w423
2026-w433
2026-w443
2026-w453

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

What changed since the last snapshot?

1 published readings changed between snapshots d1eb0cec0f6a and 868e3c39d9c7.

slope chart: tensorflow-federated, changed published values, 0, 2026-10-31 to 2026-11-07
No numeric change since 2026-10-31 for tensorflow-federated. Evidaxis snapshots · .
Snapshot values
MetricPreviousCurrentDelta
Commits per week2.22.20
Citing worksno readingno readingno reading
Weekly direct dependentsno reading1no reading
Stars2,4532,4530

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 tensorflow-federated, and why

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

Unmeasured slots
ReadingReason
Citing worksnot linked

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

tensorflow-federated

repo
Unassigned (AI-v1 census) · n = 6545 · google-parfait/tensorflow-federated
1 of 3 axes measurable · conf low
convergence gate
Convergence gate: Gate: not computable - 1 of 3 axes measurable Development velocity: measured × Citation momentum: not measurable ∅ Direct-dependents momentum (deps.dev): not measurable ∅
gate
0 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 67 within cohort p25 p50 p75 p0 p100
percentile
p67
· 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+0.33 within cohort, log-slope +0.006/wk.0+0.33
velocity z
+0.33 σ
slope
+0.006/wk
· Evidaxis snapshot · 2026-11-07
log-slope +0.006/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
2.2
Development velocity axis: measured.
total citations
no reading
Citation source: not measured.
momentum
54.2
percentile p67
commit heatmap, last 26 weeks2.2/wk
weekly commits, 26 weeks26 weeks of commits, peak 7 in a week, 19 active weeks, 47 total.week 1: 6 commitsweek 2: 2 commitsweek 3: 0 commitsweek 4: 2 commitsweek 5: 1 commitsweek 6: 1 commitsweek 7: 2 commitsweek 8: 0 commitsweek 9: 2 commitsweek 10: 1 commitsweek 11: 2 commitsweek 12: 0 commitsweek 13: 1 commitsweek 14: 0 commitsweek 15: 1 commitsweek 16: 0 commitsweek 17: 5 commitsweek 18: 4 commitsweek 19: 2 commitsweek 20: 0 commitsweek 21: 1 commitsweek 22: 2 commitsweek 23: 0 commitsweek 24: 7 commitsweek 25: 4 commitsweek 26: 1 commits
weeks
26
peak/wk
7
active
19
total
47
· Evidaxis snapshot · 2026-11-07
citations by yearCitation source: not measured.
Daily dependents count (unscored) 3 dependents 3 direct · pypi/tensorflow-federated · deps.dev · the scored m5 axis uses weekly partitions
recency-weighted swing trailing 13-week vs prior 39-week log-slope ratio +38.76, regime accelerating. prior slope +0.001, recent slope +0.056 per week. +0.001prior 39w+0.056recent 13w+38.76×
swing
+38.76×
regime
accelerating
windows
13w vs 39w
snapshot 1 of 1 · · m5
commit-axis Sharpe log-linear slope over residual std, value +0.006 with 95% CI -0.012 to +0.024, 50 degrees of freedom. CI spans zero.0+0.00695% CI -0.012, +0.024-0.012+0.024
sharpe
+0.006
95% ci
-0.012, +0.024
dof
50
snapshot 1 of 1 · · m5
commit changepoint52 weekly commit points. Changepoint at week 50 (2026-10-24), slope change -2.999 commits per week.2026-10-24
date
week
50 of 52
Δslope
-2.999/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
1
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

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