Skip to content

Resolve "Potentially unsafe external link" for Carbon Five in _includes/about-page/about-card-sponsors.html #8824

Open

Description

@computarisis

Prerequisite

  1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page.
  2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We need to fix a potentially unsafe external link by adding the attribute rel="noopener noreferrer". The problem and solution are similar to those detailed in the CodeQL alerts tracked in #5129; however, the instance addressed by this issue did not result in a CodeQL alert.

Action Items

  • Open the file _includes/about-page/about-card-sponsors.html in your IDE
  • Replace
<a href="https://www.carbonfive.com" target="_blank" alt="Carbon Five">

with

<a href="https://www.carbonfive.com" target="_blank" alt="Carbon Five" rel="noopener noreferrer">
  • Using Docker, check the /about page and confirm that the page remains the same in mobile, tablet, and desktop views as on the current website.
  • Confirm that the Carbon Five link still works and opens as expected.

Merge Team

Resources/Instructions

  1. GitHub CodeQL documentation
  2. Webpage: https://www.hackforla.org/about/
  3. This issue is part of Epic: Create issues to resolve CodeQL alerts 1- 24, 98 "Potentially unsafe external link" #5129

Activity

  1. added
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Oct 12, 2026
  2. added and removed
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Oct 17, 2026
  3. moved this from New Issue Approval to Ready for Prioritization in P: HfLA Website: Project Boardon Oct 17, 2026
  4. moved this from Ready for Prioritization to Prioritized backlog in P: HfLA Website: Project Boardon Oct 23, 2026
  5. added this to the 02. Security milestone on Oct 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions