OWASP/Nest

Describe the bug StaticSitemap.lastmod (backend/src/apps/sitemap/views/static.py) maps each static route to a model so it can compute lastmod from that model's most recent updated_at. The /repositories route is listed in BaseSitemap.STATIC_ROUTES but is missing from the path_to_model mapping, so it falls through to the datetime.now(UTC) fallback that is meant for unknown paths. As a result, the /repositories entry in the static sitemap reports the current time as its lastmod on every regeneration, instead of the latest repository update like the other seven routes. To Reproduce Steps to reproduce the behavior: Generate the static sitemap. Compare the <lastmod> value for /repositories against /chapters, /projects, etc. /repositories shows the regeneration timestamp, while the other routes show their model's latest updated_at. Expected behavior /repositories should derive its lastmod from the most recently updated Repository (Repository.objects.aggregate(Max("updated_at"))), consistent

Community & Support: LinkedIn Group · Slack #project-nest Active project leaders: Arkadii Yakovets -- GitHub · LinkedIn · Slack; Kate Golovanova -- GitHub · LinkedIn · Slack Contributing · Code of Conduct · GSoC Mentors Describe the bug The navbar does not scale properly causing layout inconsistencies on devices such as iPad Mini and iPad Pro. It should scale responsively so that all elements fit correctly across different screen sizes without breaking the layout. To Reproduce Steps to reproduce the behavior: Visit https://nest.owasp.org/. Open Chrome DevTools. Enable Device Toolbar. Select iPad Mini or iPad Pro. Observe the navbar layout. Expected behavior The navbar should scale and adapt properly on all screen, ensuring all elements fit within the available width without breaking the layout. Are you going to work on fixing this? Yes No Screenshots

Community & Support: LinkedIn Group · Slack #project-nest Active project leaders: Arkadii Yakovets -- GitHub · LinkedIn · Slack; Kate Golovanova -- GitHub · LinkedIn · Slack Contributing · Code of Conduct · GSoC Mentors Describe the bug The spacing below the Search component is inconsistent across different Nest pages in mobile viewport. Some pages include adequate vertical spacing between the search bar and the content below it, while others have little to no spacing, resulting in an inconsistent visual layout. To Reproduce Steps to reproduce the behavior: Resize to mobile viewport Navigate to the Projects/Members page, and observe that there is no vertical spacing below the Search bar Now nevigate to the Chapters/Committees page and ovserve the presence of vertical spacing Expected behavior The Search component should have consistent bottom spacing across all pages where it is used, ensuring a uniform layout and visual hierarchy. Are you going to work on fixing this? Yes

Problem Repository cards currently show stars, forks, contributors, and issues, but they do not show when the repository was last updated. Without activity information, users cannot quickly determine whether a repository is actively maintained. Proposed Solution Display the repository's last updated date on repository cards using the existing updatedAt field. Benefits Improves repository discovery. Provides activity visibility. Helps contributors identify actively maintained repositories.

Is your feature request related to a problem? Please describe. The breadcrumb trail at the top of every page is wrapped in a <div> element. Screen reader users cannot identify it as a navigation landmark using their landmark navigation shortcuts (e.g., VoiceOver rotor, NVDA elements list). This makes it harder for assistive technology users to quickly orient themselves on the page. Describe the solution you'd like Wrap the breadcrumb component in a <nav> element with aria-label="Breadcrumb" so screen readers can identify it as a navigation region and users can jump to it directly. The change is in frontend/src/components/BreadCrumbs.tsx: Line 13: <div> → <nav aria-label="Breadcrumb"> Line 56: </div> → </nav> Describe alternatives you've considered Using role="navigation" on the existing <div> — less semantic than <nav> Keeping the current <div> — works for sighted users but misses an opportunity for better screen reader support Are you going to work on implementing this?