[FEATURE] Add asset inventory page for discovered hosts and services

[utksh1]

Summary

Create an Asset Inventory page that lists discovered hosts, domains, IPs, ports, technologies, and linked findings.

Problem

SecuScan collects useful scan data, but users need a dedicated inventory view to understand their discovered attack surface across scans.

Proposed solution

Add a frontend page backed by existing or new API data that summarizes discovered assets.

Useful columns/fields:

• Hostname/domain/IP
• Open ports/services
• Related scanner/task
• Finding count and highest severity
• First seen and last seen timestamps
• Tags or source plugin where available

Acceptance criteria

• Users can view a consolidated asset inventory.
• Assets link back to related tasks/findings where possible.
• Search and severity filtering are supported.
• Empty/loading/error states are handled.
• Tests cover inventory rendering and filtering.

Suggested files

• frontend/src/pages/
• frontend/src/api.ts
• backend/secuscan/routes.py if a new endpoint is needed
• backend/secuscan/database.py if schema changes are needed
• frontend/testing/unit/

Test plan

• Run frontend tests and backend tests if API changes are included.
• Manually verify inventory with mocked or real scan results.

[virajkvk18]

Hi @utksh1 👋

I'd like to work on this issue under GSSoC 2026. I've read through CONTRIBUTING.md and confirmed this is not a duplicate.

My Approach:

Frontend:

1. Create frontend/src/pages/AssetInventory.tsx with a table view displaying: hostname/domain/IP, open ports/services, related scanner/task, finding count + highest severity, first/last seen timestamps, and source plugin/tags
2. Add search input for filtering by hostname/IP and a severity filter dropdown
3. Handle empty, loading, and error states gracefully with appropriate UI feedback
4. Link each asset row to its related tasks/findings pages using existing routes
5. Wire up data fetching via frontend/src/api.ts

Backend (if needed):

1. Add a /assets endpoint in backend/secuscan/routes.py that aggregates discovered asset data from existing scan results
2. Extend backend/secuscan/database.py minimally if an assets table or view is required

Tests:

1. Unit tests in frontend/testing/unit/ covering inventory rendering, search filtering, severity filtering, and empty/error states
2. Backend tests if new API endpoints are added

I'll first check whether existing scan data in the database is sufficient to power the inventory before adding any schema changes, keeping the backend footprint minimal.

Could you please assign this to me? Happy to sync on the data model before I start. 🚀

[aaniya22]

pls assign this to me

[virajkvk18]

Hi @utksh1 Working on it!