Evidaxis
Dated record

spikingjelly

repo · spikingjelly · paper: not linked · as of

Niche: not yet assigned.

18.5 commits per week averaged over the trailing window. No paper is linked in OpenAlex. Dependents: no admitted own package. 2 of 4 weekly observations; full commit series captured. 2,165 GitHub stars, recorded, not scored. Measured 2026-10-17 for spikingjelly; sources linked below.

commits/wk 18.5 averaged, trailing window last commit week 2026-10-11 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-10-17 no reading · deps.dev snapshot ·
stars 2,165 recorded, not scored measured · GitHub ·
Download values (CSV) JSON record Follow this system (feed) Report an error

Is spikingjelly still maintained?

18.5 commits per week averaged over the trailing window.

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

Last commit week 2026-10-11.

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

line chart: spikingjelly, weekly commits, 40 in latest week, 2025-10-19 to 2026-10-11
spikingjelly averaged 18.5 commits a week. GitHub commit_activity · .
Latest eight weeks
Week startingCommits
2026-08-2329
2026-08-3010
2026-09-067
2026-09-138
2026-09-207
2026-09-2716
2026-10-046
2026-10-1140
heatmap chart: spikingjelly, weeks with commits, 26 of 26, 2026-04-19 to 2026-10-11
26 of the last 26 captured weeks had commits for spikingjelly. GitHub commit_activity · .
All 52 weeks
Weekly commits
Week startingCommits
2025-10-193
2025-10-260
2025-11-020
2025-11-090
2025-11-164
2025-11-233
2025-11-300
2025-12-072
2025-12-140
2025-12-213
2025-12-288
2026-01-049
2026-01-116
2026-01-1812
2026-01-257
2026-02-014
2026-02-0810
2026-02-154
2026-02-220
2026-03-010
2026-03-080
2026-03-151
2026-03-221
2026-03-290
2026-04-050
2026-04-124
2026-04-1971
2026-04-2661
2026-05-0333
2026-05-1050
2026-05-1727
2026-05-2428
2026-05-3113
2026-06-074
2026-06-1431
2026-06-2141
2026-06-2848
2026-07-0574
2026-07-1211
2026-07-1917
2026-07-2621
2026-08-0218
2026-08-0931
2026-08-1629
2026-08-2329
2026-08-3010
2026-09-067
2026-09-138
2026-09-207
2026-09-2716
2026-10-046
2026-10-1140

GitHub commit_activity · period 2025-10-19 to 2026-10-11 · n = 52 weeks · method weekly totals; reconstructed dates · updated · version 4d9867e6f218-b1 · CSV

Readings

Recorded values and sources
ReadingValueΔ 4 weeksΔ 26 weeks52-week rangeInstrumentDateReproducePrevious reading
Commits per week18.5-6.715.92.6 to 40.1GitHub, trailing 12 weeks2026-10-17Public query15.6
Citing worksno readingno readingno readingno readingOpenAlex, all years2026-10-17Public queryno reading
Weekly direct dependentsno readingno readingno readingno readingWeekly direct dependents2026-10-17Public queryno reading
Daily package dependents (unscored)0no readingno reading0 to 0deps.dev REST, unscored2026-10-16Public queryno reading
Stars2,165no readingno reading2,159 to 2,165GitHub stars, unscored2026-10-17Public query2,159

Evidaxis snapshot · period 2026-10-17 · n = 1 system · method source linked readings · updated · version 4d9867e6f218-b1

How to cite spikingjelly's record?

Evidaxis. spikingjelly measurement record. Snapshot 2026-10-17. urn:evidaxis:claim:e_H8FYXB1CQ2M:m5:2026-10-17. CC0-1.0. https://evidaxis.org/e/e_H8FYXB1CQ2M/

Evidaxis · period 2026-10-17 · n = 1 system · method claim URN · updated · version 4d9867e6f218-b1

Is anyone using spikingjelly?

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): 0; captured 2026-10-16; package: pypi/spikingjelly. 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,165 GitHub stars, recorded, not scored.

Captured daily series
Unscored daily dependents, as captured
PeriodDependents
2026-w420

deps.dev · period 2026-10-17 · n = 0 partitions · method m5 own packages · updated · version 4d9867e6f218-b1 · CSV

What changed since the last snapshot?

2 published readings changed between snapshots ad5e404d4f82 and 4d9867e6f218.

slope chart: spikingjelly, changed published values, 2, 2026-10-10 to 2026-10-17
2 published values changed for spikingjelly since 2026-10-10. Evidaxis snapshots · .
Snapshot values
MetricPreviousCurrentDelta
Commits per week15.618.52.9
Citing worksno readingno readingno reading
Weekly direct dependentsno readingno readingno reading
Stars2,1592,1656

Evidaxis snapshots · period 2026-10-10 to 2026-10-17 · n = 2 partitions · method paired snapshot values · updated · version 4d9867e6f218-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-10-17 · n = 1 system · method CC0-1.0 open export · updated · version 4d9867e6f218-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 spikingjelly, 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-10-17 · n = 1 system · method measurement coverage · updated · version 4d9867e6f218-b1

    Measurement detail

    Gate, gauges, percentile, derived signals and snapshot receipt

    History: 2 of 4 weekly observations. Axis coverage: 1 of 3 axes measurable. Gate: not computable - history 2 of 4 weekly observations

    2 of 4 weekly observations; full commit series captured.

    spikingjelly

    repo
    Unassigned (AI-v1 census) · n = 6153 · spikingjelly
    1 of 3 axes measurable · conf low
    convergence gate
    Convergence gate: Gate: not computable - history 2 of 4 weekly observations Development velocity: measured × Citation momentum: not measurable ∅ Direct-dependents momentum (deps.dev): not measurable ∅
    gate
    0 of 3 axes

    Gate: not computable - history 2 of 4 weekly observations

    · Evidaxis snapshot · 2026-10-17
    Gate: not computable - history 2 of 4 weekly observations
    position in cohort distribution one of 6153 in cohort
    percentile 4 within cohort p25 p50 p75 p0 p100
    percentile
    p4
    · Evidaxis snapshot · 2026-10-17
    momentum averages present-axis z-scores; two- and three-axis scores are not strictly comparable
    velocity z
    velocity z gaugevelocity z-3.01 within cohort, log-slope -0.050/wk.0-3.01
    velocity z
    -3.01 σ
    slope
    -0.050/wk
    · Evidaxis snapshot · 2026-10-17
    log-slope -0.050/wk
    citation z Citation source: not measured.
    direct-dependents z Direct-dependents axis: no admitted own package; not measured.
    cohort
    6153
    systems measured
    weekly commits
    18.5
    Development velocity axis: measured.
    total citations
    no reading
    Citation source: not measured.
    momentum
    12.4
    percentile p4
    commit heatmap, last 26 weeks18.5/wk
    weekly commits, 26 weeks26 weeks of commits, peak 74 in a week, 26 active weeks, 731 total.week 1: 71 commitsweek 2: 61 commitsweek 3: 33 commitsweek 4: 50 commitsweek 5: 27 commitsweek 6: 28 commitsweek 7: 13 commitsweek 8: 4 commitsweek 9: 31 commitsweek 10: 41 commitsweek 11: 48 commitsweek 12: 74 commitsweek 13: 11 commitsweek 14: 17 commitsweek 15: 21 commitsweek 16: 18 commitsweek 17: 31 commitsweek 18: 29 commitsweek 19: 29 commitsweek 20: 10 commitsweek 21: 7 commitsweek 22: 8 commitsweek 23: 7 commitsweek 24: 16 commitsweek 25: 6 commitsweek 26: 40 commits
    weeks
    26
    peak/wk
    74
    active
    26
    total
    731
    · Evidaxis snapshot · 2026-10-17
    citations by yearCitation source: not measured.
    Daily dependents count (unscored) 0 dependents 0 direct · pypi/spikingjelly · deps.dev · the scored m5 axis uses weekly partitions
    recency-weighted swing trailing 13-week vs prior 39-week log-slope ratio -0.63, regime recent slope sign differs from prior window. prior slope +0.079, recent slope -0.050 per week. +0.079prior 39w-0.050recent 13w-0.63×
    swing
    -0.63×
    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.049 with 95% CI +0.011 to +0.088, 50 degrees of freedom. CI excludes zero.0+0.04995% CI +0.011, +0.088+0.011+0.088
    sharpe
    +0.049
    95% ci
    +0.011, +0.088
    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 2 of 2 · · 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-10-17 · n = 1 system · method measurement detail · updated · version 4d9867e6f218-b1 · record JSON · snapshot receipt