Evidaxis
Dated record

pytorch-lightning

repo · Lightning-AI/pytorch-lightning · paper: not linked · as of

Niche: not yet assigned.

1.6 commits per week averaged over the trailing window. No paper is linked in OpenAlex. Dependents: no admitted own package. 31,445 GitHub stars, recorded, not scored. Measured for pytorch-lightning as of 2026-11-07; sources: GitHub, OpenAlex and deps.dev where linked. Source definitions and captured readings accompany these measurements.

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

Is pytorch-lightning still maintained?

1.6 commits per week averaged over the trailing window.

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

Last commit week 2026-09-20; 6 consecutive zero weeks in the captured series.

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

line chart: pytorch-lightning, weekly commits, 0 in latest week, 2025-11-09 to 2026-11-01
pytorch-lightning averaged 1.6 commits a week. GitHub commit_activity · .
Latest eight weeks
Week startingCommits
2026-09-136
2026-09-202
2026-09-270
2026-10-040
2026-10-110
2026-10-180
2026-10-250
2026-11-010
heatmap chart: pytorch-lightning, weeks with commits, 17 of 26, 2026-05-10 to 2026-11-01
17 of the last 26 captured weeks had commits for pytorch-lightning. GitHub commit_activity · .
All 52 weeks
Weekly commits
Week startingCommits
2025-11-096
2025-11-1619
2025-11-238
2025-11-300
2025-12-077
2025-12-1436
2025-12-212
2025-12-280
2026-01-0417
2026-01-1118
2026-01-182
2026-01-2512
2026-02-012
2026-02-080
2026-02-151
2026-02-221
2026-03-0115
2026-03-081
2026-03-1528
2026-03-220
2026-03-2924
2026-04-050
2026-04-1216
2026-04-191
2026-04-262
2026-05-031
2026-05-101
2026-05-175
2026-05-2410
2026-05-318
2026-06-077
2026-06-140
2026-06-210
2026-06-287
2026-07-053
2026-07-1212
2026-07-193
2026-07-264
2026-08-022
2026-08-091
2026-08-160
2026-08-231
2026-08-307
2026-09-063
2026-09-136
2026-09-202
2026-09-270
2026-10-040
2026-10-110
2026-10-180
2026-10-250
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 week1.6-0.8-5.91.6 to 10.6GitHub, trailing 12 weeks2026-11-07Public query1.7
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)1,760no readingno reading1,709 to 1,760deps.dev REST, unscored2026-11-06Public query1,747
Stars31,44549no reading31,362 to 31,445GitHub stars, unscored2026-11-07Public query31,435

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

How to cite pytorch-lightning's record?

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

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

Is anyone using pytorch-lightning?

Dependents: no admitted own package.

Weekly dependents
PartitionDirect dependentsWeekly pointsMethod
no partitionno readingno readingm5 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): 1,760; captured 2026-11-06; package: pypi/pytorch-lightning. 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. 31,445 GitHub stars, recorded, not scored.

sparkline chart: pytorch-lightning, daily dependents, 1,760, 2026-w39 to 2026-w45
pytorch-lightning recorded 1,760 daily dependents. deps.dev REST (unscored) · .
Captured daily series
Unscored daily dependents, as captured
PeriodDependents
2026-w391,709
2026-w401,720
2026-w411,728
2026-w421,732
2026-w431,741
2026-w441,749
2026-w451,760

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: pytorch-lightning, changed published values, 2, 2026-10-31 to 2026-11-07
2 published values changed for pytorch-lightning since 2026-10-31. Evidaxis snapshots · .
Snapshot values
MetricPreviousCurrentDelta
Commits per week1.71.6-0.1
Citing worksno readingno readingno reading
Weekly direct dependentsno readingno readingno reading
Stars31,43531,44510

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-lightning, and why

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

Unmeasured slots
ReadingReason
Citing worksnot linked
Weekly direct dependentsoutside panel

Dependents: no admitted own package.

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-lightning

repo
Unassigned (AI-v1 census) · n = 6545 · Lightning-AI/pytorch-lightning
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 0 within cohort p25 p50 p75 p0 p100
percentile
p0
· 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-3.25 within cohort, log-slope -0.063/wk.0-3.25
velocity z
-3.25 σ
slope
-0.063/wk
· Evidaxis snapshot · 2026-11-07
log-slope -0.063/wk
citation z Citation source: not measured.
direct-dependents z Direct-dependents axis: no admitted own package; not measured.
cohort
6545
systems measured
weekly commits
1.6
Development velocity axis: measured.
total citations
no reading
Citation source: not measured.
momentum
9.4
percentile p0
commit heatmap, last 26 weeks1.6/wk
weekly commits, 26 weeks26 weeks of commits, peak 12 in a week, 17 active weeks, 82 total.week 1: 1 commitsweek 2: 5 commitsweek 3: 10 commitsweek 4: 8 commitsweek 5: 7 commitsweek 6: 0 commitsweek 7: 0 commitsweek 8: 7 commitsweek 9: 3 commitsweek 10: 12 commitsweek 11: 3 commitsweek 12: 4 commitsweek 13: 2 commitsweek 14: 1 commitsweek 15: 0 commitsweek 16: 1 commitsweek 17: 7 commitsweek 18: 3 commitsweek 19: 6 commitsweek 20: 2 commitsweek 21: 0 commitsweek 22: 0 commitsweek 23: 0 commitsweek 24: 0 commitsweek 25: 0 commitsweek 26: 0 commits
weeks
26
peak/wk
12
active
17
total
82
· Evidaxis snapshot · 2026-11-07
citations by yearCitation source: not measured.
Daily dependents count (unscored) 1,760 dependents 670 direct, 1,165 indirect · pypi/pytorch-lightning · deps.dev · the scored m5 axis uses weekly partitions
recency-weighted swing trailing 13-week vs prior 39-week log-slope ratio +7.06, regime accelerating. prior slope -0.014, recent slope -0.098 per week. -0.014prior 39w-0.098recent 13w+7.06×
swing
+7.06×
regime
accelerating
windows
13w vs 39w
snapshot 1 of 1 · · m5
commit-axis Sharpe log-linear slope over residual std, value -0.027 with 95% CI -0.045 to -0.009, 50 degrees of freedom. CI spans zero.0-0.02795% CI -0.045, -0.009-0.045-0.009
sharpe
-0.027
95% ci
-0.045, -0.009
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: no admitted own package; not measured.

Coverage state
out_of_panel
Cohort z
no axis
OLS slope
no reading
Theil-Sen slope
no reading
Latest direct dependents
no reading
Confirmed-clean points
no reading
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