Evidaxis
Dated record

pytorch-forecasting

repo · sktime/pytorch-forecasting · paper: not linked · as of

Niche: not yet assigned.

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

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

Is pytorch-forecasting still maintained?

3.2 commits per week averaged over the trailing window.

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

Last commit week 2026-10-25; 1 consecutive zero weeks in the captured series.

Commits in the latest captured week vs 4 weeks earlier: -3 · vs 26 weeks earlier: -2 · 52-week range: 0 to 9 commits in an individual week.

line chart: pytorch-forecasting, weekly commits, 0 in latest week, 2025-11-09 to 2026-11-01
pytorch-forecasting averaged 3.2 commits a week. GitHub commit_activity · .
Latest eight weeks
Week startingCommits
2026-09-136
2026-09-203
2026-09-274
2026-10-043
2026-10-114
2026-10-183
2026-10-254
2026-11-010
heatmap chart: pytorch-forecasting, weeks with commits, 24 of 26, 2026-05-10 to 2026-11-01
24 of the last 26 captured weeks had commits for pytorch-forecasting. GitHub commit_activity · .
All 52 weeks
Weekly commits
Week startingCommits
2025-11-090
2025-11-161
2025-11-230
2025-11-301
2025-12-071
2025-12-144
2025-12-210
2025-12-280
2026-01-045
2026-01-115
2026-01-184
2026-01-252
2026-02-011
2026-02-082
2026-02-151
2026-02-220
2026-03-019
2026-03-085
2026-03-153
2026-03-224
2026-03-291
2026-04-054
2026-04-123
2026-04-191
2026-04-260
2026-05-032
2026-05-101
2026-05-173
2026-05-243
2026-05-313
2026-06-074
2026-06-145
2026-06-212
2026-06-281
2026-07-050
2026-07-121
2026-07-191
2026-07-261
2026-08-023
2026-08-092
2026-08-163
2026-08-232
2026-08-304
2026-09-062
2026-09-136
2026-09-203
2026-09-274
2026-10-043
2026-10-114
2026-10-183
2026-10-254
2026-11-010

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 week3.20.40.41.8 to 3.4GitHub, trailing 12 weeks2026-11-07Public query3.2
Citing worksno readingno readingno readingno readingOpenAlex, all years2026-11-07Public queryno reading
Weekly direct dependents7no readingno reading7 to 7Weekly direct dependents2026-11-07Public queryno reading
Daily package dependents (unscored)no readingno readingno readingno readingdeps.dev REST, unscorednot capturedPublic queryno reading
Stars5,01110no reading4,997 to 5,011GitHub stars, unscored2026-11-07Public query5,008

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

How to cite pytorch-forecasting's record?

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

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

Is anyone using pytorch-forecasting?

deps.dev: 7 direct dependents.

Weekly dependents
PartitionDirect dependentsWeekly pointsMethod
no partition71m5 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. 5,011 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?

2 published readings changed between snapshots d1eb0cec0f6a and 868e3c39d9c7.

slope chart: pytorch-forecasting, changed published values, 1, 2026-10-31 to 2026-11-07
1 published values changed for pytorch-forecasting since 2026-10-31. Evidaxis snapshots · .
Snapshot values
MetricPreviousCurrentDelta
Commits per week3.23.20
Citing worksno readingno readingno reading
Weekly direct dependentsno reading7no reading
Stars5,0085,0113

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 pytorch-forecasting, 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: 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

pytorch-forecasting

repo
Unassigned (AI-v1 census) · n = 6545 · sktime/pytorch-forecasting
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 68 within cohort p25 p50 p75 p0 p100
percentile
p68
· 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.42 within cohort, log-slope +0.008/wk.0+0.42
velocity z
+0.42 σ
slope
+0.008/wk
· Evidaxis snapshot · 2026-11-07
log-slope +0.008/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
3.2
Development velocity axis: measured.
total citations
no reading
Citation source: not measured.
momentum
55.3
percentile p68
commit heatmap, last 26 weeks3.2/wk
weekly commits, 26 weeks26 weeks of commits, peak 6 in a week, 24 active weeks, 68 total.week 1: 1 commitsweek 2: 3 commitsweek 3: 3 commitsweek 4: 3 commitsweek 5: 4 commitsweek 6: 5 commitsweek 7: 2 commitsweek 8: 1 commitsweek 9: 0 commitsweek 10: 1 commitsweek 11: 1 commitsweek 12: 1 commitsweek 13: 3 commitsweek 14: 2 commitsweek 15: 3 commitsweek 16: 2 commitsweek 17: 4 commitsweek 18: 2 commitsweek 19: 6 commitsweek 20: 3 commitsweek 21: 4 commitsweek 22: 3 commitsweek 23: 4 commitsweek 24: 3 commitsweek 25: 4 commitsweek 26: 0 commits
weeks
26
peak/wk
6
active
24
total
68
· Evidaxis snapshot · 2026-11-07
citations by yearCitation source: not measured.
recency-weighted swing trailing 13-week vs prior 39-week log-slope ratio -2.74, regime recent slope sign differs from prior window. prior slope +0.008, recent slope -0.022 per week. +0.008prior 39w-0.022recent 13w-2.74×
swing
-2.74×
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.018 with 95% CI -0.004 to +0.039, 50 degrees of freedom. CI spans zero.0+0.01895% CI -0.004, +0.039-0.004+0.039
sharpe
+0.018
95% ci
-0.004, +0.039
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
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
7
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