Evidaxis
Dated record

pytriton

repo · triton-inference-server/pytriton · paper: not linked · as of

Niche: not yet assigned.

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

commits/wk 0 averaged, trailing window Δ vs 26 weeks ago: 0 measured · GitHub ·
citations no paper linked all years, indexed to date no reading · OpenAlex ·
direct dependents 2 weekly axis input; partition 2026-11-07 measured · deps.dev snapshot ·
stars 849 recorded, not scored measured · GitHub ·
Download values (CSV) JSON record Follow this system (feed) Report an error

Is pytriton still maintained?

0 commits per week averaged over the trailing window.

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

No commits observed since 2025-11-09.

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

line chart: pytriton, weekly commits, 0 in latest week, 2025-11-09 to 2026-11-01
pytriton averaged 0 commits a week. GitHub commit_activity · .
Latest eight weeks
Week startingCommits
2026-09-130
2026-09-200
2026-09-270
2026-10-040
2026-10-110
2026-10-180
2026-10-250
2026-11-010
heatmap chart: pytriton, weeks with commits, 0 of 26, 2026-05-10 to 2026-11-01
0 of the last 26 captured weeks had commits for pytriton. 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-290
2026-04-050
2026-04-120
2026-04-190
2026-04-260
2026-05-030
2026-05-100
2026-05-170
2026-05-240
2026-05-310
2026-06-070
2026-06-140
2026-06-210
2026-06-280
2026-07-050
2026-07-120
2026-07-190
2026-07-260
2026-08-020
2026-08-090
2026-08-160
2026-08-230
2026-08-300
2026-09-060
2026-09-130
2026-09-200
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 week0000 to 0GitHub, trailing 12 weeks2026-11-07Public query0
Citing worksno readingno readingno readingno readingOpenAlex, all years2026-11-07Public queryno reading
Weekly direct dependents2no readingno reading2 to 2Weekly direct dependents2026-11-07Public queryno reading
Daily package dependents (unscored)no readingno readingno readingno readingdeps.dev REST, unscorednot capturedPublic queryno reading
Stars8490no reading849 to 850GitHub stars, unscored2026-11-07Public query849

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

How to cite pytriton's record?

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

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

Is anyone using pytriton?

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

Weekly dependents
PartitionDirect dependentsWeekly pointsMethod
no partition21m5 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. 849 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?

1 published readings changed between snapshots d1eb0cec0f6a and 868e3c39d9c7.

slope chart: pytriton, changed published values, 0, 2026-10-31 to 2026-11-07
No numeric change since 2026-10-31 for pytriton. Evidaxis snapshots · .
Snapshot values
MetricPreviousCurrentDelta
Commits per week000
Citing worksno readingno readingno reading
Weekly direct dependentsno reading2no reading
Stars8498490

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 pytriton, 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

pytriton

repo
Unassigned (AI-v1 census) · n = 6545 · triton-inference-server/pytriton
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 52 within cohort p25 p50 p75 p0 p100
percentile
p52
· 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.07 within cohort, log-slope +0.000/wk.0+0.07
velocity z
+0.07 σ
slope
+0.000/wk
· Evidaxis snapshot · 2026-11-07
log-slope +0.000/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
0
Development velocity axis: measured.
total citations
no reading
Citation source: not measured.
momentum
50.9
percentile p52
commit heatmap, last 26 weeks0/wk
weekly commits, 26 weeks26 weeks of commits, peak 0 in a week, 0 active weeks, 0 total.week 1: 0 commitsweek 2: 0 commitsweek 3: 0 commitsweek 4: 0 commitsweek 5: 0 commitsweek 6: 0 commitsweek 7: 0 commitsweek 8: 0 commitsweek 9: 0 commitsweek 10: 0 commitsweek 11: 0 commitsweek 12: 0 commitsweek 13: 0 commitsweek 14: 0 commitsweek 15: 0 commitsweek 16: 0 commitsweek 17: 0 commitsweek 18: 0 commitsweek 19: 0 commitsweek 20: 0 commitsweek 21: 0 commitsweek 22: 0 commitsweek 23: 0 commitsweek 24: 0 commitsweek 25: 0 commitsweek 26: 0 commits
weeks
26
peak/wk
0
active
0
total
0
· 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.00, regime flat. prior slope +0.000, recent slope +0.000 per week. +0.000prior 39w+0.000recent 13w+0.00×
swing
+0.00×
regime
flat
windows
13w vs 39w
snapshot 1 of 1 · · m5
commit Sharpereserved: <26 non-zero commit weeks
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
2
reserved
4

shipped

  • recency-swing
  • commit-changepoint

reserved

  • commit-sharpe
  • 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
2
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