Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for agent platform teams hitting the latency and cost wall of one-VM-per-run sandboxes: benchmark one fan-out workload first, then compare spawn times, isolation, and operational overhead against your current container or VM runner.
Who should use it
Who should skip it
Skip deeplethe/forkd if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
deeplethe/forkd is tracked by RepoRadar as a developer tool in the AI Infrastructure section. First seen 2026-06-19; the source record was last checked on 2026-06-19. The current verdict is 'watch' with a Gold tier and expert setup difficulty. deeplethe/forkd leads on workflow potential (9.2) and novelty (9.0); its lowest signal is setup ease (6.2), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The deeplethe/forkd record combines a 8.8/10 composite score with separate popularity (54.0), risk (conditional), and setup (expert) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It is built to execute and snapshot workloads inside microVMs, so review guest image provenance, mounted paths, and network egress before using it for untrusted agent runs.