Despair-Games/poketernity Check time for Despair-Games/poketernity over 10 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. 805 ms
▼ -97.9%
since Sep 9
800 ms–815 ms
Scanner time for Despair-Games/poketernity over 10 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. 156 ms
▼ -5.7%
since Sep 11
147 ms–161 ms
Parse diagnostics for Despair-Games/poketernity over 10 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 10 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 10 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. 652
15
errors · 218 warnings ·
419
info
▲
+8
errors
since Sep 14
dyc3/opentogethertube Check time for dyc3/opentogethertube over 10 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. 89 ms
▼ -57.2%
since Sep 9
79 ms–95 ms
Scanner time for dyc3/opentogethertube over 10 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 10 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 10 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 10 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. 9
8
errors · 1 warnings ·
0
info
indico/indico Check time for indico/indico over 10 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. 86 ms
▲ +12.1%
since Sep 16
84 ms–90 ms
Scanner time for indico/indico over 10 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 indico/indico over 10 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 10 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 10 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. 138
138
errors · 0 warnings ·
0
info
novuhq/novu Check time for novuhq/novu over 10 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.60 s
▼ -38.2%
since Sep 9
1.57 s–1.62 s
Scanner time for novuhq/novu over 10 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. 497 ms
▲ +7.2%
since Sep 14
489 ms–507 ms
Parse diagnostics for novuhq/novu over 10 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 10 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 10 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,805
237
errors · 4147 warnings ·
421
info
▼
−187
warnings
since Sep 16
promptfoo/promptfoo Check time for promptfoo/promptfoo over 10 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.05 s
▼ -22.1%
since Sep 9
15.02 s–15.10 s
Scanner time for promptfoo/promptfoo over 10 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. 331 ms
▲ +5.6%
since Sep 14
329 ms–353 ms
Parse diagnostics for promptfoo/promptfoo over 10 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 10 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 10 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. 183
1
errors · 182 warnings ·
0
info
▲
+1
errors
since Sep 16
scverse/scanpy Check time for scverse/scanpy over 10 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. 11 ms
▲ +15.1%
since Sep 14
10 ms–11 ms
Scanner time for scverse/scanpy over 10 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 10 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 10 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 10 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
3
errors · 0 warnings ·
0
info
vercel/vercel Check time for vercel/vercel over 10 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. 817 ms
▼ -72.0%
since Sep 7
808 ms–842 ms
Scanner time for vercel/vercel over 10 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
▲ +8.5%
latest run only
14 ms–17 ms
Parse diagnostics for vercel/vercel over 10 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 10 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 10 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. 103
76
errors · 27 warnings ·
0
info
vikejs/vike Check time for vikejs/vike over 10 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. 130 ms
▼ -85.7%
since Sep 7
122 ms–134 ms
Scanner time for vikejs/vike over 10 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
▲ +9.0%
since Sep 16
3 ms–4 ms
Parse diagnostics for vikejs/vike over 10 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 10 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 10 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
50
errors · 0 warnings ·
0
info
▼
−1
errors
since Sep 11
anyproto/anytype-ts Check time for anyproto/anytype-ts over 10 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. 270 ms
▼ -82.5%
since Sep 9
262 ms–274 ms
Scanner time for anyproto/anytype-ts over 10 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
▲ +6.7%
since Sep 9
9 ms–11 ms
Parse diagnostics for anyproto/anytype-ts over 10 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 10 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 10 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
c15t/c15t Check time for c15t/c15t over 10 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.36 s
▼ -84.3%
since Sep 14
8.35 s–8.57 s
Scanner time for c15t/c15t over 10 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
▲ +6.9%
since Sep 9
2 ms–4 ms
Parse diagnostics for c15t/c15t over 10 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 10 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 10 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,103
661
errors · 1160 warnings ·
282
info
crbnos/carbon Check time for crbnos/carbon over 10 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.05 s
▼ -87.3%
since Sep 7
1.02 s–1.06 s
Scanner time for crbnos/carbon over 10 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 10 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 10 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 10 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. 655
61
errors · 594 warnings ·
0
info
▲
+1
warnings
since Sep 7
django/django Check time for django/django over 10 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. 58 ms
▼ -38.9%
since Sep 7
58 ms–59 ms
Scanner time for django/django over 10 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 ms
▲ +9.4%
since Sep 9
6 ms–8 ms
Parse diagnostics for django/django over 10 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 10 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 10 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. 0
0
errors · 0 warnings ·
0
info
elizaOS/eliza Check time for elizaOS/eliza over 10 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.40 s
▼ -73.8%
since Sep 9
8.30 s–8.47 s
Scanner time for elizaOS/eliza over 10 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 elizaOS/eliza over 10 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 10 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 10 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,415
495
errors · 866 warnings ·
54
info
▲
+2
errors
since Sep 9
EpicenterHQ/epicenter Check time for EpicenterHQ/epicenter over 10 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. 261 ms
▼ -89.1%
since Sep 14
258 ms–282 ms
Scanner time for EpicenterHQ/epicenter over 10 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 ms
▲ +6.3%
since Sep 9
3 ms–4 ms
Parse diagnostics for EpicenterHQ/epicenter over 10 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 10 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 10 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. 338
60
errors · 269 warnings ·
9
info
▼
−2
errors
since Sep 11
fern-api/fern Check time for fern-api/fern over 10 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. 966 ms
▼ -52.4%
since Sep 9
951 ms–984 ms
Scanner time for fern-api/fern over 10 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 10 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 10 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 10 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
▲
+2
warnings
since Sep 7
microsoft/fast Check time for microsoft/fast over 10 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. 277 ms
▼ -58.7%
since Sep 9
274 ms–305 ms
Scanner time for microsoft/fast over 10 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 ms
▲ +6.3%
since Sep 9
6 ms–7 ms
Parse diagnostics for microsoft/fast over 10 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 10 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 10 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. 436
236
errors · 198 warnings ·
2
info
▼
−3
warnings
since Sep 7
prisma/prisma-next Check time for prisma/prisma-next over 10 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.31 s
▼ -29.1%
since Sep 14
1.21 s–1.34 s
Scanner time for prisma/prisma-next over 10 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 prisma/prisma-next over 10 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 10 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 10 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,086
18
errors · 14 warnings ·
1054
info
▲
+2
warnings
since Sep 11
rivet-dev/rivet Check time for rivet-dev/rivet over 10 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. 514 ms
▼ -66.5%
since Sep 9
512 ms–542 ms
Scanner time for rivet-dev/rivet over 10 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. 129 ms
-10.7%
127 ms–137 ms
Parse diagnostics for rivet-dev/rivet over 10 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 10 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 10 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,269
707
errors · 553 warnings ·
9
info
▲
+1
warnings
since Sep 7
superset-sh/superset Check time for superset-sh/superset over 10 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.22 s
▼ -25.8%
since Sep 9
1.21 s–1.24 s
Scanner time for superset-sh/superset over 10 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 10 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 10 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 10 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. 303
220
errors · 81 warnings ·
2
info
▲
+2
warnings
since Sep 7
TEN-framework/ten-framework Check time for TEN-framework/ten-framework over 10 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.96 s
-17.6%
4.74 s–4.97 s
Scanner time for TEN-framework/ten-framework over 10 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. 40 ms
▲ +13.1%
since Sep 11
31 ms–46 ms
Parse diagnostics for TEN-framework/ten-framework over 10 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 10 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 10 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. 10,888
6798
errors · 3444 warnings ·
646
info
baptisteArno/typebot.io Check time for baptisteArno/typebot.io over 10 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. 315 ms
▼ -16.6%
since Sep 7
310 ms–325 ms
Scanner time for baptisteArno/typebot.io over 10 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 10 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 10 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 10 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. 35
10
errors · 25 warnings ·
0
info
Byline-CMS/bylinecms.dev Check time for Byline-CMS/bylinecms.dev over 10 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. 422 ms
▼ -48.8%
since Sep 9
392 ms–441 ms
Scanner time for Byline-CMS/bylinecms.dev over 10 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 Byline-CMS/bylinecms.dev over 10 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 10 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 10 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. 303
0
errors · 180 warnings ·
123
info
▼
−1
warnings
since Sep 16
chakra-ui/ark Check time for chakra-ui/ark over 10 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. 508 ms
-11.5%
485 ms–533 ms
Scanner time for chakra-ui/ark over 10 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 chakra-ui/ark over 10 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 10 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 10 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,439
17
errors · 5100 warnings ·
322
info
CherryHQ/cherry-studio Check time for CherryHQ/cherry-studio over 10 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.61 s
▼ -87.2%
since Sep 9
2.60 s–2.66 s
Scanner time for CherryHQ/cherry-studio over 10 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 CherryHQ/cherry-studio over 10 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 10 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 10 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. 11,887
11823
errors · 64 warnings ·
0
info
cline/cline Check time for cline/cline over 10 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.93 s
▼ -67.1%
since Sep 9
1.88 s–1.94 s
Scanner time for cline/cline over 10 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 10 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 10 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 10 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,290
200
errors · 221 warnings ·
1869
info
coder/coder Check time for coder/coder over 10 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. 612 ms
▼ -94.9%
since Sep 9
606 ms–623 ms
Scanner time for coder/coder over 10 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 10 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 10 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 10 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. 171
145
errors · 20 warnings ·
6
info
cosscom/coss Check time for cosscom/coss over 10 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. 212 ms
▼ -80.7%
since Sep 7
208 ms–230 ms
Scanner time for cosscom/coss over 10 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 cosscom/coss over 10 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 10 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 10 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. 43
34
errors · 3 warnings ·
6
info
discordjs/discord.js Check time for discordjs/discord.js over 10 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. 373 ms
▼ -90.0%
since Sep 9
366 ms–378 ms
Scanner time for discordjs/discord.js over 10 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 discordjs/discord.js over 10 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 10 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 10 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,301
828
errors · 1296 warnings ·
177
info
▼
−16
errors
since Sep 7
freelensapp/freelens Check time for freelensapp/freelens over 10 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. 250 ms
▼ -25.5%
since Sep 9
249 ms–261 ms
Scanner time for freelensapp/freelens over 10 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 freelensapp/freelens over 10 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 10 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 10 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
5
errors · 0 warnings ·
0
info
liam-hq/liam Check time for liam-hq/liam over 10 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. 228 ms
-10.1%
225 ms–239 ms
Scanner time for liam-hq/liam over 10 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 10 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 10 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 10 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. 72
26
errors · 43 warnings ·
3
info
material-extensions/vscode-material-icon-theme Check time for material-extensions/vscode-material-icon-theme over 10 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. 61 ms
▼ -74.8%
since Sep 7
60 ms–61 ms
Scanner time for material-extensions/vscode-material-icon-theme over 10 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 material-extensions/vscode-material-icon-theme over 10 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 10 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 10 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. 0
0
errors · 0 warnings ·
0
info
microsoft/FluidFramework Check time for microsoft/FluidFramework over 10 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. 717 ms
▼ -92.9%
since Sep 9
712 ms–739 ms
Scanner time for microsoft/FluidFramework over 10 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 10 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 10 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 10 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
5
errors · 0 warnings ·
0
info
▼
−9
errors
since Sep 11
midday-ai/midday Check time for midday-ai/midday over 10 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. 459 ms
▼ -64.9%
since Sep 7
454 ms–475 ms
Scanner time for midday-ai/midday over 10 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
▼ -14.3%
since Sep 9
2 ms–3 ms
Parse diagnostics for midday-ai/midday over 10 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 10 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 10 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
5
errors · 9 warnings ·
0
info
mrousavy/react-native-vision-camera Check time for mrousavy/react-native-vision-camera over 10 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. 59 ms
▼ -32.2%
since Sep 9
58 ms–60 ms
Scanner time for mrousavy/react-native-vision-camera over 10 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 mrousavy/react-native-vision-camera over 10 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 mrousavy/react-native-vision-camera over 10 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 mrousavy/react-native-vision-camera over 10 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. 19
2
errors · 17 warnings ·
0
info
nhost/nhost Check time for nhost/nhost over 10 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. 957 ms
▼ -67.9%
since Sep 9
947 ms–984 ms
Scanner time for nhost/nhost over 10 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 10 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 10 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 10 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,650
2127
errors · 486 warnings ·
37
info
oblador/react-native-vector-icons Check time for oblador/react-native-vector-icons over 10 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. 39 ms
▼ -20.0%
since Sep 9
37 ms–41 ms
Scanner time for oblador/react-native-vector-icons over 10 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 10 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 10 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 10 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
0
errors · 0 warnings ·
1
info
ParabolInc/parabol Check time for ParabolInc/parabol over 10 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. 489 ms
▼ -27.4%
since Sep 7
480 ms–526 ms
Scanner time for ParabolInc/parabol over 10 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 ParabolInc/parabol over 10 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 10 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 10 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. 80
71
errors · 9 warnings ·
0
info
podman-desktop/podman-desktop Check time for podman-desktop/podman-desktop over 10 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. 560 ms
▼ -96.3%
since Sep 9
557 ms–576 ms
Scanner time for podman-desktop/podman-desktop over 10 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 10 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 10 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 10 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,043
835
errors · 4437 warnings ·
771
info
pollinations/pollinations Check time for pollinations/pollinations over 10 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. 306 ms
▼ -81.5%
since Sep 9
301 ms–321 ms
Scanner time for pollinations/pollinations over 10 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 10 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 10 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 10 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. 549
299
errors · 233 warnings ·
17
info
stagewise-io/stagewise Check time for stagewise-io/stagewise over 10 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. 436 ms
▼ -59.1%
since Sep 9
416 ms–460 ms
Scanner time for stagewise-io/stagewise over 10 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 stagewise-io/stagewise over 10 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 10 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 10 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. 27
12
errors · 15 warnings ·
0
info
web-infra-dev/modern.js Check time for web-infra-dev/modern.js over 10 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. 235 ms
▼ -39.7%
since Sep 9
233 ms–261 ms
Scanner time for web-infra-dev/modern.js over 10 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
▼ -13.7%
since Sep 14
15 ms–17 ms
Parse diagnostics for web-infra-dev/modern.js over 10 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 10 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 10 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. 850
496
errors · 343 warnings ·
11
info
▼
−1
errors
since Sep 16
wevm/wagmi Check time for wevm/wagmi over 10 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. 200 ms
▼ -74.0%
since Sep 7
193 ms–215 ms
Scanner time for wevm/wagmi over 10 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 10 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 10 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 10 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. 37
24
errors · 11 warnings ·
2
info
▼
−4
errors
since Sep 11
withastro/astro Check time for withastro/astro over 10 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. Sep 9 Sep 18 300 ms
▼ -30.3%
since Sep 7
294 ms–322 ms
Scanner time for withastro/astro over 10 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. Sep 9 Sep 18 Parse diagnostics for withastro/astro over 10 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. Sep 9 Sep 18 Panics for withastro/astro over 10 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. Sep 9 Sep 18 Diagnostics by severity for withastro/astro over 10 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. Sep 9 Sep 18 1
0
errors · 1 warnings ·
0
info
▼
−1
errors
since Sep 11
