You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(publish): retry cargo publish on transient registry index lag (#622)
Performance
Binary
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
3.3ms
112.0ms
27.7ms
3.5ms
3.1ms
13.1 MB
mono-50-5k
ferrflow
3.0ms
508.4ms
104.5ms
3.0ms
2.7ms
12.9 MB
mono-large
ferrflow
4.4ms
1017.7ms
210.1ms
4.6ms
3.8ms
15.1 MB
mono-medium
ferrflow
3.0ms
60.8ms
15.2ms
2.8ms
2.8ms
13.1 MB
mono-small
ferrflow
2.9ms
17.9ms
5.0ms
2.5ms
2.5ms
12.8 MB
single
ferrflow
2.5ms
16.5ms
4.6ms
2.4ms
2.5ms
12.9 MB
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show ferrflow. Cross-tool comparisons live in the Npm section.
Docker
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
-
-
218.7ms
186.9ms
187.1ms
42.9 MB
mono-50-5k
ferrflow
-
-
317.5ms
185.9ms
183.8ms
45.1 MB
mono-large
ferrflow
-
-
443.3ms
186.7ms
188.3ms
43.5 MB
mono-medium
ferrflow
-
-
201.9ms
184.8ms
182.3ms
43.4 MB
mono-small
ferrflow
-
-
186.4ms
184.7ms
185.9ms
43.5 MB
single
ferrflow
-
-
189.4ms
185.5ms
185.0ms
43.3 MB
Note: no competitor publishes a first-party Docker image that is comparable to ghcr.io/ferrlabs/ferrflow (a single static binary). Wrapping the Node tools in node:lts would only re-time node startup + npm + the tool already measured in the Npm section, so this section is intentionally limited to ferrflow.
fix(build): sync Cargo.lock to the 5.20.0 manifest version (#616)
Refactoring
refactor(obs): migrate src/monorepo/ diagnostics to tracing macros (#615)
Performance
Binary
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
3.3ms
110.6ms
26.9ms
3.3ms
2.9ms
13.1 MB
mono-50-5k
ferrflow
2.9ms
505.3ms
104.4ms
3.1ms
2.6ms
12.9 MB
mono-large
ferrflow
4.2ms
1026.4ms
212.4ms
4.4ms
3.8ms
15.1 MB
mono-medium
ferrflow
3.1ms
60.2ms
14.7ms
3.0ms
2.7ms
12.8 MB
mono-small
ferrflow
2.7ms
17.8ms
4.9ms
2.5ms
2.5ms
13.0 MB
single
ferrflow
2.5ms
16.4ms
4.6ms
2.5ms
2.4ms
12.9 MB
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show ferrflow. Cross-tool comparisons live in the Npm section.
Docker
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
-
-
216.1ms
185.8ms
181.4ms
45.6 MB
mono-50-5k
ferrflow
-
-
309.3ms
183.5ms
183.3ms
45.3 MB
mono-large
ferrflow
-
-
444.2ms
183.8ms
182.6ms
45.1 MB
mono-medium
ferrflow
-
-
196.4ms
179.8ms
182.4ms
42.9 MB
mono-small
ferrflow
-
-
181.7ms
178.5ms
181.3ms
45.9 MB
single
ferrflow
-
-
182.9ms
184.7ms
179.4ms
43.2 MB
Note: no competitor publishes a first-party Docker image that is comparable to ghcr.io/ferrlabs/ferrflow (a single static binary). Wrapping the Node tools in node:lts would only re-time node startup + npm + the tool already measured in the Npm section, so this section is intentionally limited to ferrflow.
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show ferrflow. Cross-tool comparisons live in the Npm section.
Docker
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
-
-
173.9ms
156.1ms
155.1ms
43.2 MB
mono-50-5k
ferrflow
-
-
242.5ms
157.6ms
156.6ms
44.9 MB
mono-large
ferrflow
-
-
336.6ms
156.7ms
155.5ms
43.9 MB
mono-medium
ferrflow
-
-
167.1ms
152.4ms
154.2ms
43.1 MB
mono-small
ferrflow
-
-
157.3ms
151.2ms
153.5ms
43.0 MB
single
ferrflow
-
-
159.6ms
153.4ms
154.9ms
43.4 MB
Note: no competitor publishes a first-party Docker image that is comparable to ghcr.io/ferrlabs/ferrflow (a single static binary). Wrapping the Node tools in node:lts would only re-time node startup + npm + the tool already measured in the Npm section, so this section is intentionally limited to ferrflow.
feat(npm): publish CLI as unscoped ferrflow with @ferrflow/* platform packages (#606)
feat(publish): auto-scope by triggering tag, accept multiple packages and --all (#602)
Bug Fixes
fix(deps): bump memmap2 to 0.9.11 (RUSTSEC-2026-0186) (#604)
Performance
Binary
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
3.7ms
119.2ms
28.9ms
3.7ms
3.5ms
12.9 MB
mono-50-5k
ferrflow
3.2ms
539.4ms
113.1ms
3.1ms
2.9ms
12.7 MB
mono-large
ferrflow
4.7ms
1081.2ms
228.7ms
4.9ms
4.2ms
12.9 MB
mono-medium
ferrflow
3.2ms
63.6ms
16.0ms
3.2ms
3.0ms
12.7 MB
mono-small
ferrflow
2.8ms
18.5ms
5.7ms
2.7ms
2.6ms
12.7 MB
single
ferrflow
2.8ms
16.9ms
4.8ms
2.6ms
2.5ms
12.6 MB
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show ferrflow. Cross-tool comparisons live in the Npm section.
Docker
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
-
-
218.6ms
190.0ms
190.7ms
49.5 MB
mono-50-5k
ferrflow
-
-
318.8ms
181.5ms
189.6ms
43.8 MB
mono-large
ferrflow
-
-
462.2ms
186.1ms
187.3ms
43.3 MB
mono-medium
ferrflow
-
-
199.9ms
185.2ms
183.8ms
45.2 MB
mono-small
ferrflow
-
-
189.6ms
184.0ms
181.5ms
43.1 MB
single
ferrflow
-
-
186.5ms
186.8ms
181.9ms
46.7 MB
Note: no competitor publishes a first-party Docker image that is comparable to ghcr.io/ferrlabs/ferrflow (a single static binary). Wrapping the Node tools in node:lts would only re-time node startup + npm + the tool already measured in the Npm section, so this section is intentionally limited to ferrflow.
feat(cli): add --jobs / FERRFLOW_JOBS to control parallelism (#598)
Bug Fixes
perf(git): use commit-graph for revision walks (#596)
Performance
Binary
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
3.1ms
108.9ms
26.6ms
3.3ms
3.0ms
12.9 MB
mono-50-5k
ferrflow
2.9ms
502.1ms
104.1ms
2.9ms
2.5ms
12.6 MB
mono-large
ferrflow
4.3ms
1013.6ms
210.2ms
4.2ms
3.6ms
12.5 MB
mono-medium
ferrflow
2.8ms
58.1ms
14.7ms
2.8ms
2.6ms
12.7 MB
mono-small
ferrflow
2.6ms
17.0ms
5.0ms
2.5ms
2.3ms
12.7 MB
single
ferrflow
2.5ms
15.7ms
4.4ms
2.4ms
2.3ms
12.7 MB
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show ferrflow. Cross-tool comparisons live in the Npm section.
Docker
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
-
-
215.3ms
179.5ms
179.5ms
43.2 MB
mono-50-5k
ferrflow
-
-
303.9ms
180.5ms
179.1ms
43.1 MB
mono-large
ferrflow
-
-
444.2ms
183.9ms
181.5ms
45.6 MB
mono-medium
ferrflow
-
-
195.1ms
178.8ms
179.0ms
43.5 MB
mono-small
ferrflow
-
-
183.7ms
182.6ms
180.7ms
44.1 MB
single
ferrflow
-
-
186.1ms
178.2ms
178.6ms
43.6 MB
Note: no competitor publishes a first-party Docker image that is comparable to ghcr.io/ferrlabs/ferrflow (a single static binary). Wrapping the Node tools in node:lts would only re-time node startup + npm + the tool already measured in the Npm section, so this section is intentionally limited to ferrflow.
perf(forge): parallelize per-tag release creation with a capped rayon pool (#595)
Performance
Binary
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
3.4ms
113.0ms
27.2ms
3.4ms
3.0ms
12.5 MB
mono-50-5k
ferrflow
2.9ms
512.8ms
103.9ms
2.8ms
2.7ms
12.5 MB
mono-large
ferrflow
4.2ms
1035.3ms
218.4ms
4.6ms
3.9ms
12.5 MB
mono-medium
ferrflow
2.8ms
60.0ms
14.4ms
2.8ms
2.6ms
12.5 MB
mono-small
ferrflow
2.4ms
18.4ms
4.7ms
2.4ms
2.4ms
12.5 MB
single
ferrflow
2.4ms
16.6ms
4.4ms
2.2ms
2.3ms
12.5 MB
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show ferrflow. Cross-tool comparisons live in the Npm section.
Docker
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
-
-
221.4ms
186.1ms
185.7ms
44.0 MB
mono-50-5k
ferrflow
-
-
319.8ms
185.2ms
186.2ms
43.7 MB
mono-large
ferrflow
-
-
459.6ms
185.9ms
186.8ms
43.2 MB
mono-medium
ferrflow
-
-
199.7ms
186.4ms
185.2ms
44.2 MB
mono-small
ferrflow
-
-
186.2ms
185.6ms
186.9ms
45.6 MB
single
ferrflow
-
-
186.2ms
183.9ms
182.0ms
44.1 MB
Note: no competitor publishes a first-party Docker image that is comparable to ghcr.io/ferrlabs/ferrflow (a single static binary). Wrapping the Node tools in node:lts would only re-time node startup + npm + the tool already measured in the Npm section, so this section is intentionally limited to ferrflow.
refactor(monorepo): share HEAD-ancestor cache through orphan-strategy tag lookups (#594)
Performance
Binary
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
3.2ms
108.3ms
26.1ms
3.3ms
3.1ms
12.5 MB
mono-50-5k
ferrflow
2.8ms
506.2ms
102.1ms
2.7ms
2.6ms
12.5 MB
mono-large
ferrflow
4.1ms
1024.7ms
212.9ms
4.2ms
3.7ms
12.3 MB
mono-medium
ferrflow
2.7ms
58.7ms
14.2ms
2.7ms
2.5ms
12.6 MB
mono-small
ferrflow
2.3ms
17.3ms
4.7ms
2.4ms
2.2ms
12.5 MB
single
ferrflow
2.3ms
16.1ms
4.3ms
2.2ms
2.2ms
12.3 MB
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show ferrflow. Cross-tool comparisons live in the Npm section.
Docker
Fixture
Tool
check
release-dry-run
tag
validate
version
Peak RSS
mono-100-1k
ferrflow
-
-
210.8ms
179.5ms
182.8ms
43.4 MB
mono-50-5k
ferrflow
-
-
312.0ms
180.7ms
182.8ms
44.0 MB
mono-large
ferrflow
-
-
456.6ms
186.3ms
181.4ms
46.2 MB
mono-medium
ferrflow
-
-
196.6ms
182.7ms
185.6ms
45.7 MB
mono-small
ferrflow
-
-
186.7ms
182.4ms
184.1ms
45.9 MB
single
ferrflow
-
-
187.2ms
181.4ms
180.8ms
46.6 MB
Note: no competitor publishes a first-party Docker image that is comparable to ghcr.io/ferrlabs/ferrflow (a single static binary). Wrapping the Node tools in node:lts would only re-time node startup + npm + the tool already measured in the Npm section, so this section is intentionally limited to ferrflow.