Skip to content

Implement security audit report viewer and logging functionality#418

Open
Ahmedscreativeverse wants to merge 1 commit into
benelabs:mainfrom
Ahmedscreativeverse:Implement-security-audit-report-viewer
Open

Implement security audit report viewer and logging functionality#418
Ahmedscreativeverse wants to merge 1 commit into
benelabs:mainfrom
Ahmedscreativeverse:Implement-security-audit-report-viewer

Conversation

@Ahmedscreativeverse
Copy link
Copy Markdown

closes #356

Reviewing the actual changed files so the PR documentation is accurate and complete.

PR Documentation

Summary

Implemented the backend portion of the Security Audit Report Viewer feature.

What changed

  • audit.rs

    • Added AuditService::list_events(...) and AuditService::get_event(...)
    • Added new API handlers:
      • GET /api/v1/audit/reports
      • GET /api/v1/audit/reports/:id
    • Kept POST /api/v1/audit/log for audit event ingestion
    • Added request/query DTOs and response types for audit report viewing
  • main.rs

    • Registered new audit route namespace under /api/v1/audit
    • Added AuditService initialization
    • Included audit routes in OpenAPI docs
  • audit_tests.rs

    • Added coverage for:
      • audit log ingestion handler
      • audit report list endpoint
      • single audit report retrieval
  • README.md

    • Documented the new Security Audit Report Viewer API endpoints
  • error.rs

    • Fixed broken AppError implementation so backend error handling compiles cleanly
  • mod.rs

    • Exported the new audit service module
  • Cargo.lock

    • Began cleaning duplicate package entries that were blocking cargo check

Testing

  • New backend tests added for audit API behavior
  • Full backend compilation could not be completed because Cargo.lock still has duplicate package entries causing parse failure:
    • compression-codecs
    • const-oid

Notes

  • This PR is backend-only; no frontend UI exists in the workspace yet.
  • The implementation follows the existing Axum/service architecture and OpenAPI conventions.
  • Security review is not yet complete; the current focus is on API surface and persistence.

Suggested PR description

Add Security Audit Report Viewer backend support

  • Implement audit reporting service with list and retrieve endpoints
  • Wire /api/v1/audit routes into backend router
  • Add OpenAPI documentation for audit report viewer
  • Extend backend tests for audit ingestion and report retrieval
  • Fix broken backend error module
  • Document API in backend README

Notes: Cargo.lock currently contains duplicate package entries that must be resolved before cargo check can complete.

If you want, I can also generate a full GitHub PR body with checklist, changelog, and testing commands.

@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented May 29, 2026

@Ahmedscreativeverse Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Frontend] Implement security audit report viewer

1 participant