Skip to content

Epic: Create issues to resolve CodeQL alerts 1- 24, 98 "Potentially unsafe external link" #5129

Closed
0 of 3 issues completed

Description

@roslynwythe

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 resolve CodeQL code alerts 1 - 24 of type Potentially unsafe external link.

Dependencies (child issues - this issue will remain open until all these issues are completed)

These address instances which were not flagged by CodeQL:

Action Items

Issue Template

#5129 (comment)

Activity

  1. github-actions commented on Aug 2, 2023

    @github-actions
  2. changed the title [-]Audit/Recommendation for CodeQL query `[QUERY NAME]` and associated alerts ###[/-] [+]Audit/Recommendation for CodeQL query `Potentially unsafe external link` and associated alerts[/+] on Aug 2, 2023
  3. 90 remaining items

  4. daras-cu commented on Oct 4, 2026

    @daras-cu
    Member

    @computarisis I unassigned you from your other IM issue as that one was for the design team, you can work on this one instead. There are three more issues that need to be created, under 'These address instances which were not flagged by CodeQL:'.

    There is a template linked at the bottom of this issue which you can use as a starting point, but you'll need to edit it a little since there is no actual CodeQL alert associated with the issues you'll be making. The attribute that needs to be added to the links is the same. If you'd like to create one issue first, I can sign off on the format before you proceed with the others. Let me know if you have any questions.

  5. computarisis commented on Oct 4, 2026

    @computarisis
    Member

    ETA: Mon, Oct 5th by 8PM ET

    Availability: Everyday after 8PM ET

  6. castillios commented on Oct 17, 2026

    @castillios
    Member

    Hi @computarisis, thanks creating those issues. I reviewed all three and have marked them all as ready for prioritization.

  7. moved this from In progress (actively working) to QA in P: HfLA Website: Project Boardon Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions