material-extensions/vscode-material-icon-theme Check time for material-extensions/vscode-material-icon-theme over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 48 ms
▼ -23.7%
since Oct 26
47 ms–52 ms
Scanner time for material-extensions/vscode-material-icon-theme over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 3 ms
▲ +7.2%
since Nov 2
3 ms
Parse diagnostics for material-extensions/vscode-material-icon-theme over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for material-extensions/vscode-material-icon-theme over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for material-extensions/vscode-material-icon-theme over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 14
14
errors · 0 warnings ·
0
info
▲
+14
errors
since Oct 7
ParabolInc/parabol Check time for ParabolInc/parabol over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 338 ms
▼ -26.3%
since Oct 14
333 ms–349 ms
Scanner time for ParabolInc/parabol over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 169 ms
▲ +2679.0%
since Oct 14
167 ms–173 ms
Parse diagnostics for ParabolInc/parabol over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for ParabolInc/parabol over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for ParabolInc/parabol over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 2,191
1901
errors · 20 warnings ·
270
info
▲
+1
errors
since Nov 2
TEN-framework/ten-framework Check time for TEN-framework/ten-framework over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 2.53 s
▼ -50.2%
since Oct 28
2.48 s–2.56 s
Scanner time for TEN-framework/ten-framework over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 355 ms
▼ -13.5%
since Oct 26
351 ms–366 ms
Parse diagnostics for TEN-framework/ten-framework over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for TEN-framework/ten-framework over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for TEN-framework/ten-framework over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 12,533
8441
errors · 3446 warnings ·
646
info
▲
+39
errors
since Nov 2
web-infra-dev/modern.js Check time for web-infra-dev/modern.js over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 198 ms
▼ -14.3%
since Sep 18
187 ms–203 ms
Scanner time for web-infra-dev/modern.js over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 17 ms
▼ -11.0%
latest run only
16 ms–18 ms
Parse diagnostics for web-infra-dev/modern.js over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for web-infra-dev/modern.js over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for web-infra-dev/modern.js over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 998
579
errors · 408 warnings ·
11
info
▲
+4
errors
since Nov 2
baptisteArno/typebot.io Check time for baptisteArno/typebot.io over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 226 ms
▼ -12.1%
since Oct 28
223 ms–235 ms
Scanner time for baptisteArno/typebot.io over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for baptisteArno/typebot.io over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for baptisteArno/typebot.io over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for baptisteArno/typebot.io over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 50
22
errors · 28 warnings ·
0
info
▲
+3
warnings
since Oct 7
Byline-CMS/bylinecms.dev Check time for Byline-CMS/bylinecms.dev over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 287 ms
▼ -7.1%
since Oct 23
283 ms–294 ms
Scanner time for Byline-CMS/bylinecms.dev over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 18 ms
▲ +20.1%
since Sep 18
17 ms–18 ms
Parse diagnostics for Byline-CMS/bylinecms.dev over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for Byline-CMS/bylinecms.dev over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for Byline-CMS/bylinecms.dev over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 482
173
errors · 186 warnings ·
123
info
▼
−6
errors
since Oct 26
c15t/c15t Check time for c15t/c15t over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 4.48 s
▼ -51.5%
since Oct 30
4.24 s–4.50 s
Scanner time for c15t/c15t over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 137 ms
▼ -12.3%
since Oct 16
136 ms–141 ms
Parse diagnostics for c15t/c15t over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for c15t/c15t over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for c15t/c15t over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 2,364
921
errors · 1161 warnings ·
282
info
▲
+1
warnings
since Oct 7
chakra-ui/ark Check time for chakra-ui/ark over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 371 ms
▼ -28.7%
since Oct 26
363 ms–413 ms
Scanner time for chakra-ui/ark over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 10 ms
▲ +25.2%
since Sep 18
9 ms–12 ms
Parse diagnostics for chakra-ui/ark over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for chakra-ui/ark over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for chakra-ui/ark over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 5,486
65
errors · 5097 warnings ·
324
info
▲
+2
info
since Oct 7
CherryHQ/cherry-studio Check time for CherryHQ/cherry-studio over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 2.07 s
▼ -20.8%
since Oct 30
2.06 s–2.26 s
Scanner time for CherryHQ/cherry-studio over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 465 ms
▲ +5802.1%
since Oct 14
454 ms–520 ms
Parse diagnostics for CherryHQ/cherry-studio over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for CherryHQ/cherry-studio over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for CherryHQ/cherry-studio over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 14,383
12127
errors · 2256 warnings ·
0
info
▲
+2,192
warnings
since Oct 7
coder/coder Check time for coder/coder over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 447 ms
▼ -5.1%
since Nov 3
442 ms–460 ms
Scanner time for coder/coder over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for coder/coder over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for coder/coder over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for coder/coder over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 689
656
errors · 27 warnings ·
6
info
▲
+7
warnings
since Oct 7
cosscom/coss No report in latest run Check time for cosscom/coss over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 223 ms
+1.1%
219 ms–239 ms
Scanner time for cosscom/coss over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 106 ms
▲ +2610.8%
since Oct 7
104 ms–114 ms
Parse diagnostics for cosscom/coss over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for cosscom/coss over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for cosscom/coss over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 2,350
93
errors · 2251 warnings ·
6
info
▲
+59
errors
since Oct 7
crbnos/carbon Check time for crbnos/carbon over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 763 ms
▼ -23.0%
since Oct 18
755 ms–791 ms
Scanner time for crbnos/carbon over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for crbnos/carbon over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for crbnos/carbon over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for crbnos/carbon over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 656
62
errors · 594 warnings ·
0
info
▲
+1
errors
since Oct 7
Despair-Games/poketernity Check time for Despair-Games/poketernity over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 601 ms
▼ -20.6%
since Oct 28
600 ms–606 ms
Scanner time for Despair-Games/poketernity over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 133 ms
▼ -14.6%
since Oct 19
126 ms–136 ms
Parse diagnostics for Despair-Games/poketernity over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for Despair-Games/poketernity over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for Despair-Games/poketernity over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 670
22
errors · 229 warnings ·
419
info
▲
+1
warnings
since Oct 26
discordjs/discord.js Check time for discordjs/discord.js over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 281 ms
▼ -15.2%
since Oct 17
259 ms–282 ms
Scanner time for discordjs/discord.js over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 2 ms
▲ +11.6%
since Sep 28
2 ms–3 ms
Parse diagnostics for discordjs/discord.js over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for discordjs/discord.js over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for discordjs/discord.js over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 2,327
852
errors · 1298 warnings ·
177
info
▲
+2
warnings
since Oct 7
django/django Check time for django/django over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 22 ms
▼ -53.6%
since Oct 26
21 ms–23 ms
Scanner time for django/django over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for django/django over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for django/django over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for django/django over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 1
1
errors · 0 warnings ·
0
info
▲
+1
errors
since Oct 23
dyc3/opentogethertube Check time for dyc3/opentogethertube over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 72 ms
▼ -11.4%
since Oct 17
71 ms–75 ms
Scanner time for dyc3/opentogethertube over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for dyc3/opentogethertube over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for dyc3/opentogethertube over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for dyc3/opentogethertube over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 56
39
errors · 8 warnings ·
9
info
▲
+7
warnings
since Oct 7
elizaOS/eliza Check time for elizaOS/eliza over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 6.19 s
▼ -5.6%
since Nov 2
6.15 s–6.34 s
Scanner time for elizaOS/eliza over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 73 ms
▲ +8.0%
since Oct 2
72 ms–77 ms
Parse diagnostics for elizaOS/eliza over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for elizaOS/eliza over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for elizaOS/eliza over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 2,182
1180
errors · 948 warnings ·
54
info
▲
+82
warnings
since Oct 7
EpicenterHQ/epicenter Check time for EpicenterHQ/epicenter over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 186 ms
▼ -21.1%
since Oct 21
170 ms–194 ms
Scanner time for EpicenterHQ/epicenter over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 56 ms
▲ +1667.3%
since Oct 14
52 ms–56 ms
Parse diagnostics for EpicenterHQ/epicenter over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for EpicenterHQ/epicenter over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for EpicenterHQ/epicenter over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 615
76
errors · 530 warnings ·
9
info
▲
+11
errors
since Oct 12
freelensapp/freelens Check time for freelensapp/freelens over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 216 ms
-5.0%
211 ms–222 ms
Scanner time for freelensapp/freelens over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 5 ms
▲ +8.8%
since Sep 23
4 ms–5 ms
Parse diagnostics for freelensapp/freelens over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for freelensapp/freelens over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for freelensapp/freelens over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 71
71
errors · 0 warnings ·
0
info
▼
−6
errors
since Nov 2
indico/indico Check time for indico/indico over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Scanner time for indico/indico over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 3 ms
▲ +11.9%
since Sep 25
3 ms–4 ms
Parse diagnostics for indico/indico over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for indico/indico over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for indico/indico over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 145
145
errors · 0 warnings ·
0
info
▲
+16
errors
since Oct 7
microsoft/fast Check time for microsoft/fast over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 318 ms
+15.5%
310 ms–322 ms
Scanner time for microsoft/fast over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 8 ms
▲ +9.2%
since Sep 21
7 ms–8 ms
Parse diagnostics for microsoft/fast over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for microsoft/fast over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for microsoft/fast over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 3,670
3433
errors · 235 warnings ·
2
info
▲
+37
warnings
since Oct 7
microsoft/FluidFramework Check time for microsoft/FluidFramework over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 645 ms
▼ -9.9%
since Oct 26
636 ms–663 ms
Scanner time for microsoft/FluidFramework over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for microsoft/FluidFramework over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for microsoft/FluidFramework over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for microsoft/FluidFramework over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 89
89
errors · 0 warnings ·
0
info
▲
+2
errors
since Oct 30
nhost/nhost Check time for nhost/nhost over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 1.59 s
▼ -6.7%
since Oct 28
1.58 s–1.61 s
Scanner time for nhost/nhost over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for nhost/nhost over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for nhost/nhost over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for nhost/nhost over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 4,665
4141
errors · 487 warnings ·
37
info
▲
+1
warnings
since Oct 7
novuhq/novu Check time for novuhq/novu over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 1.26 s
▼ -15.8%
since Oct 14
1.24 s–1.27 s
Scanner time for novuhq/novu over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 414 ms
▼ -9.7%
since Oct 18
407 ms–418 ms
Parse diagnostics for novuhq/novu over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for novuhq/novu over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for novuhq/novu over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 4,984
406
errors · 4157 warnings ·
421
info
▲
+10
warnings
since Oct 7
oblador/react-native-vector-icons Check time for oblador/react-native-vector-icons over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 26 ms
▼ -76.9%
since Oct 26
26 ms–29 ms
Scanner time for oblador/react-native-vector-icons over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for oblador/react-native-vector-icons over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for oblador/react-native-vector-icons over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for oblador/react-native-vector-icons over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 98
97
errors · 0 warnings ·
1
info
▲
+1
errors
since Oct 30
podman-desktop/podman-desktop Check time for podman-desktop/podman-desktop over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 403 ms
▼ -24.9%
since Oct 26
400 ms–408 ms
Scanner time for podman-desktop/podman-desktop over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for podman-desktop/podman-desktop over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for podman-desktop/podman-desktop over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for podman-desktop/podman-desktop over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 6,351
1094
errors · 4486 warnings ·
771
info
▲
+49
warnings
since Oct 7
pollinations/pollinations Check time for pollinations/pollinations over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 232 ms
▼ -11.7%
since Sep 18
219 ms–244 ms
Scanner time for pollinations/pollinations over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for pollinations/pollinations over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for pollinations/pollinations over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for pollinations/pollinations over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 557
307
errors · 233 warnings ·
17
info
▲
+8
errors
since Oct 7
prisma/prisma-next Check time for prisma/prisma-next over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 856 ms
▼ -18.1%
since Nov 2
851 ms–976 ms
Scanner time for prisma/prisma-next over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 28 ms
▲ +9.0%
since Oct 17
28 ms–31 ms
Parse diagnostics for prisma/prisma-next over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for prisma/prisma-next over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for prisma/prisma-next over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 1,746
678
errors · 14 warnings ·
1054
info
▼
−81
errors
since Oct 28
promptfoo/promptfoo Check time for promptfoo/promptfoo over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 3.11 s
▼ -79.9%
since Nov 3
3.10 s–3.20 s
Scanner time for promptfoo/promptfoo over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 263 ms
▼ -12.2%
since Oct 18
259 ms–323 ms
Parse diagnostics for promptfoo/promptfoo over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for promptfoo/promptfoo over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for promptfoo/promptfoo over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 185
3
errors · 182 warnings ·
0
info
▲
+2
errors
since Oct 12
rivet-dev/rivet Check time for rivet-dev/rivet over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 442 ms
▼ -12.7%
since Oct 14
420 ms–462 ms
Scanner time for rivet-dev/rivet over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 118 ms
+7.9%
113 ms–129 ms
Parse diagnostics for rivet-dev/rivet over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for rivet-dev/rivet over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for rivet-dev/rivet over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 1,289
721
errors · 559 warnings ·
9
info
▲
+14
errors
since Oct 7
scverse/scanpy Check time for scverse/scanpy over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Scanner time for scverse/scanpy over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for scverse/scanpy over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for scverse/scanpy over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for scverse/scanpy over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 92
92
errors · 0 warnings ·
0
info
▲
+39
errors
since Oct 30
stagewise-io/stagewise Check time for stagewise-io/stagewise over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 290 ms
-0.2%
285 ms–309 ms
Scanner time for stagewise-io/stagewise over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 98 ms
▲ +3106.1%
since Oct 7
96 ms–103 ms
Parse diagnostics for stagewise-io/stagewise over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for stagewise-io/stagewise over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for stagewise-io/stagewise over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 1,909
230
errors · 1679 warnings ·
0
info
▲
+1,664
warnings
since Oct 7
superset-sh/superset Check time for superset-sh/superset over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 920 ms
▼ -17.2%
since Oct 16
899 ms–925 ms
Scanner time for superset-sh/superset over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for superset-sh/superset over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for superset-sh/superset over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for superset-sh/superset over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 518
434
errors · 82 warnings ·
2
info
▲
+1
warnings
since Oct 7
vercel/vercel Check time for vercel/vercel over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 625 ms
▼ -21.4%
since Oct 19
623 ms–632 ms
Scanner time for vercel/vercel over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 15 ms
▲ +6.1%
since Sep 28
15 ms–16 ms
Parse diagnostics for vercel/vercel over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for vercel/vercel over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for vercel/vercel over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 120
76
errors · 44 warnings ·
0
info
▲
+17
warnings
since Oct 7
vikejs/vike Check time for vikejs/vike over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 104 ms
▼ -37.4%
since Oct 26
95 ms–105 ms
Scanner time for vikejs/vike over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for vikejs/vike over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for vikejs/vike over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for vikejs/vike over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 91
91
errors · 0 warnings ·
0
info
▲
+31
errors
since Oct 7
wevm/wagmi Check time for wevm/wagmi over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 161 ms
▼ -14.1%
since Oct 21
156 ms–163 ms
Scanner time for wevm/wagmi over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for wevm/wagmi over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for wevm/wagmi over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for wevm/wagmi over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 546
533
errors · 11 warnings ·
2
info
▲
+64
errors
since Oct 30
withastro/astro Check time for withastro/astro over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 303 ms
▲ +6.4%
since Sep 21
299 ms–321 ms
Scanner time for withastro/astro over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 5 ms
▲ +14.7%
since Sep 21
5 ms–6 ms
Parse diagnostics for withastro/astro over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for withastro/astro over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for withastro/astro over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 82
76
errors · 6 warnings ·
0
info
▲
+5
warnings
since Oct 7
anyproto/anytype-ts Check time for anyproto/anytype-ts over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 210 ms
▼ -21.3%
since Oct 28
204 ms–213 ms
Scanner time for anyproto/anytype-ts over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for anyproto/anytype-ts over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for anyproto/anytype-ts over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for anyproto/anytype-ts over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 1,652
1649
errors · 3 warnings ·
0
info
cline/cline Check time for cline/cline over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 1.38 s
▼ -19.7%
since Nov 2
1.38 s–1.39 s
Scanner time for cline/cline over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for cline/cline over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for cline/cline over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for cline/cline over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 2,490
383
errors · 238 warnings ·
1869
info
▼
−6
errors
since Oct 28
cosscom/ui Check time for cosscom/ui over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 179 ms
▼ -12.4%
since Oct 18
170 ms–186 ms
Scanner time for cosscom/ui over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 94 ms
▼ -10.5%
since Oct 26
93 ms–102 ms
Parse diagnostics for cosscom/ui over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for cosscom/ui over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for cosscom/ui over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 2,509
118
errors · 2365 warnings ·
26
info
▼
−7
errors
since Oct 23
fern-api/fern Check time for fern-api/fern over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 658 ms
▼ -5.0%
since Oct 26
655 ms–682 ms
Scanner time for fern-api/fern over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for fern-api/fern over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for fern-api/fern over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for fern-api/fern over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 18
16
errors · 2 warnings ·
0
info
liam-hq/liam Check time for liam-hq/liam over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 182 ms
▼ -14.4%
since Sep 18
179 ms–197 ms
Scanner time for liam-hq/liam over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for liam-hq/liam over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for liam-hq/liam over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for liam-hq/liam over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 145
99
errors · 43 warnings ·
3
info
▼
−7
errors
since Oct 28
midday-ai/midday Check time for midday-ai/midday over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 340 ms
▼ -23.1%
since Oct 14
335 ms–352 ms
Scanner time for midday-ai/midday over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Parse diagnostics for midday-ai/midday over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Panics for midday-ai/midday over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Diagnostics by severity for midday-ai/midday over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. 38
29
errors · 9 warnings ·
0
info
▼
−1
errors
since Oct 21
mrousavy/react-native-vision-camera Check time for mrousavy/react-native-vision-camera over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Oct 12 Nov 4 40 ms
▼ -28.8%
since Oct 28
39 ms–43 ms
Scanner time for mrousavy/react-native-vision-camera over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Oct 12 Nov 4 Parse diagnostics for mrousavy/react-native-vision-camera over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Oct 12 Nov 4 Panics for mrousavy/react-native-vision-camera over 30 runs Runs progress from left to right. Timing lines show medians, with bands
covering the minimum to maximum samples. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Oct 12 Nov 4 Diagnostics by severity for mrousavy/react-native-vision-camera over 30 runs Rule diagnostics stacked from bottom to top:
Errors, Warnings, Info. Gaps indicate unavailable
observations, not zero. Use the run inspector or historical data table for
exact values and keyboard access. Oct 12 Nov 4 33
16
errors · 17 warnings ·
0
info
▼
−3
errors
since Oct 21
