Across 1,580 analyzed functions in FuelLabs/fuels-rs — a Rust SDK for the Fuel network — all 26 highest-risk functions that surface at the top of the risk list trace back to docs/theme/highlight.js, a bundled third-party syntax highlighter. The top-ranked function, ‘E’, carries an activity risk score of 18.5 with cyclomatic complexity of 48 and fan-out of 39, sitting in the ‘debt’ quadrant — meaning this is structural debt with a high blast radius if ever touched, not a sign of active churn in the SDK itself. Filtering out vendored files is the single most important step before drawing conclusions about the health of the first-party Rust code.
The table below ranks functions by activity-weighted risk — a score that multiplies structural complexity by recent commit frequency. A function that is both hard to understand (high cyclomatic complexity) and actively changing is a higher priority than one that is complex but untouched. CC = cyclomatic complexity (independent execution paths); ND = max nesting depth; FO = fan-out (distinct callees).
Top 5 Hotspots
| Function | File | Risk | CC | ND | FO |
|---|---|---|---|---|---|
E | docs/theme/highlight.js | 18.5 | 48 | 3 | 39 |
<anonymous> | docs/theme/highlight.js | 16.2 | 140 | 3 | 139 |
<anonymous> | docs/theme/highlight.js | 16.2 | 72 | 3 | 68 |
q | docs/theme/highlight.js | 15.9 | 32 | 2 | 23 |
w | docs/theme/highlight.js | 15.5 | 24 | 3 | 7 |
Codemod / Tooling Files in Results
All five entries in the top_hotspots list belong to docs/theme/highlight.js, which is a minified, vendored copy of the highlight.js syntax-highlighting library bundled into the fuels-rs documentation theme. Minified bundles produce artificially extreme complexity scores — CC 140 and fan-out 139 on a single anonymous function — because minification collapses what was originally many smaller functions into dense, multi-path blobs. To exclude this file and surface real first-party Rust hotspots, add the following to your .hotspotsrc.json: { "exclude": ["docs/theme/"] }.
Hotspot Analysis
E — docs/theme/highlight.js
Based on its file path and minified single-letter name, ‘E’ is almost certainly a core dispatch or tokenization routine inside the bundled highlight.js library used for documentation syntax highlighting. Its cyclomatic complexity of 48 means 48 independent execution paths — each a required test case — while its fan-out of 39 indicates it calls 39 distinct functions, making it a structural hub whose internal behavior ripples broadly across the bundled library. It sits in the ‘debt’ quadrant, meaning this is long-accumulated structural complexity that hasn’t been actively changed — not a live regression risk — but its blast radius is substantial if the docs theme is ever upgraded.
Recommendation: Exclude docs/theme/highlight.js from your hotspots configuration immediately so it stops masking signals from first-party Rust code; do not attempt to refactor this file directly — update or replace the highlight.js bundle via its upstream release instead.
<anonymous> — docs/theme/highlight.js
This anonymous function — one of two in the same file — registers an extreme cyclomatic complexity of 140 with a fan-out of 139, making it the single most structurally complex entry in the entire dataset. At CC 140, it represents 140 independent execution paths and 139 distinct callees, a profile consistent with a large language-definition registry or a master dispatch table inside a minified syntax-highlighting bundle. Like all entries from this file, it falls in the ‘debt’ quadrant with an activity risk of 16.2, indicating this structural weight has accumulated over time without recent modification to the SDK docs theme.
Recommendation: Do not attempt to refactor this anonymous function in isolation; the correct remediation is replacing the vendored bundle with a maintained upstream version of highlight.js and adding the file to your .hotspotsrc.json excludes.
q — docs/theme/highlight.js
The minified function ‘q’, also inside the bundled highlight.js, carries a cyclomatic complexity of 32 and fan-out of 23, with an activity risk of 15.9 — the fourth-highest in the repo. Its ‘exit_heavy’ pattern flag indicates multiple return or exit paths, which compound the test-coverage burden of an already branchy function. As a ‘debt’-quadrant entry, it represents structural complexity that has not been recently modified; the risk is realized only if someone updates the docs theme without understanding the internal complexity of the bundle.
Recommendation: Treat ‘q’ as a vendor artifact — exclude the file from analysis rather than planning any refactoring effort against it.
Patterns Found
Antipatterns detected across the top functions in this snapshot:
| Pattern | Occurrences |
|---|---|
exit_heavy | 5 |
god_function | 3 |
stale_complex | 3 |
long_function | 2 |
cyclic_hub | 1 |
hub_function | 1 |
These labels belong to two tiers — Tier 1 (structural): complex_branching, deeply_nested, exit_heavy, long_function, god_function. Tier 2 (relational/temporal): hub_function, cyclic_hub, middle_man, neighbor_risk, stale_complex, churn_magnet, shotgun_target, volatile_god.
Key Takeaways
- Add ‘docs/theme/’ to your .hotspotsrc.json exclude list immediately — all 5 top hotspots are vendored highlight.js artifacts, and they are hiding the true risk profile of the 1,580-function Rust codebase.
- The anonymous function in docs/theme/highlight.js has a cyclomatic complexity of 140 and fan-out of 139 — numbers that would be alarming in first-party code, but here they are a measurement artifact of minification, not a signal about SDK quality.
- Once vendored files are excluded, focus triage on the 26 highest-risk and 177 high-risk functions in the first-party Rust code, prioritizing any ‘fire’-quadrant entries (high complexity AND high recent activity) over ‘debt’-quadrant entries.
Reproduce This Analysis
git clone https://github.com/FuelLabs/fuels-rs
cd fuels-rs
git checkout 137fa28aa6305cf8da5a11501c586742546f6e8c
hotspots analyze . --mode snapshot --explain-patterns --forceTo run the same analysis on your own codebase, run hotspots analyze . --mode snapshot in any local git repo — no configuration required.
Hotspots highlights structural and activity risk — not “bad code.” Findings are a prioritization aid, not a bug predictor. Editorial policy →