Skip to content

fix(alert detected type): don't default to leaked secret #208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 23 commits into from
Jan 27, 2025

Conversation

alex-mcgovern
Copy link
Collaborator

@alex-mcgovern alex-mcgovern commented Jan 27, 2025

  • fixes a minor nit in getIssueDetectedType where we were defaulting to "leaked" secret if an alert was not malicious
  • fixes a failing test in AlertsTable caused by isColumnHeader being applied to the time, rather than the "type" of alert

Base automatically changed from alerts-table-refactor to main January 27, 2025 12:07
@kantord kantord enabled auto-merge (squash) January 27, 2025 13:14
@coveralls
Copy link
Collaborator

coveralls commented Jan 27, 2025

Pull Request Test Coverage Report for Build 12990646744

Details

  • 6 of 7 (85.71%) changed or added relevant lines in 5 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.07%) to 68.305%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/lib/utils.ts 2 3 66.67%
Totals Coverage Status
Change from base Build 12988609897: 0.07%
Covered Lines: 768
Relevant Lines: 1023

💛 - Coveralls

@kantord kantord merged commit 0e64263 into main Jan 27, 2025
8 checks passed
@kantord kantord deleted the fix/issue-detected-type/don't-default-to-leaked-secret branch January 27, 2025 14:09
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.

4 participants