SpecterOps / SpecterOps/Nemesis
[Bug]: File Content tab bar overflows container when file has many enrichment tabs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 997
- Forks
- 104
- PR merge metrics
- No merged PRs in 30d
Description
Bug Summary
File Content tab bar overflows container when file has many enrichment tabs breaking page layout
Steps to Reproduce
- Start Nemesis with LLM support enabled
- Upload a .NET assembly (e.g., SharpHound.exe) via the CLI or web UI
- Wait for enrichment to complete (dotnet_service produces decompiled.zip and strings.txt)
- Navigate to the file's detail page in the frontend
- Observe the tab bar area now has 6+ tabs (Strings, .NET Assembly Analysis, Enrichment - pe, Enrichment - dotnet, Enrichment - dotnet_service, Hex) plus action buttons (View Raw, View Decompiled Source Code)
Expected Behavior
The tab bar should remain within the card boundaries either scrolling horizontally or wrapping
Actual Behavior
The TabsList has no overflow handling.
When tabs + action buttons exceed the container width, the entire tab bar overflows its parent, pushing content outside the visible viewport and breaking the page layout.
Nemesis Version
v2.2.2
Operating System
Linux (Ubuntu/Debian)
Docker Version
NA
Relevant Logs
Screenshots
Additional Context
The root cause should be in FileViewer.jsx
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in FileViewer.jsx and inspect how the TabsList and action buttons are laid out when six or more tabs are present. Reproduce the issue with a .NET assembly such as SharpHound.exe and verify that the tab bar stays within the card boundaries by scrolling horizontally or wrapping without pushing content outside the viewport.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 62/100