Skip to content

Conversation

@cx-dhanashree-wani
Copy link

By submitting a PR to this repository, you agree to the terms within the Checkmarx Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.

Description

Added Fix to the UI test cases which were failing due to some UI changes

References

Include supporting link to GitHub Issue/PR number

Testing

Describe how this change was tested. Be specific about anything not tested and reasons why. If this solution has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.

Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.

Checklist

  • I have added documentation for new/changed functionality in this PR (if applicable).
  • All active GitHub checks for tests, formatting, and security are passing
  • The correct base branch is being used

cx-aniket-shinde and others added 30 commits September 26, 2025 15:07
commit ac6ffa8
Author: atishj99 <[email protected]>
Date:   Tue Oct 7 16:37:09 2025 +0530

    welcome page changes

commit b520731
Author: atishj99 <[email protected]>
Date:   Mon Oct 6 12:38:26 2025 +0530

    New UI for  settings panel

commit 65c4015
Author: Atish Jadhav <[email protected]>
Date:   Mon Sep 29 13:21:23 2025 +0530

    Feature/secret detection (AST-105453) (#347)

    * Added Secret Detection result support with enhanced vulnerability details panel

    * Added SCS test coverage for ResultNode and ResultsTreeFactory

    * Using latest java wrapper version 2.4.10

    * Update KICS engine label, enable SCS vulnerability grouping, improve triage change display, and correct JetBrains Help URL

    * ResultNode/ResultTree: refactor label creation and centralize engine-type display mapping

commit 45b2bb9
Author: ast-phoenix <[email protected]>
Date:   Fri Sep 26 14:30:58 2025 +0300

    Update AST CLI Java Wrapper to version 2.4.10 (#349)

    Co-authored-by: github-actions <[email protected]>

commit fea7864
Author: Aniket Shinde <[email protected]>
Date:   Wed Sep 24 12:21:03 2025 +0530

    Added code bashing image (#346)

commit 5ce6be5
Author: Atish Jadhav <[email protected]>
Date:   Fri Aug 29 17:43:26 2025 +0530

    Remove deprecated code from IntelliJ Plugin (AST-109419) (#344)

    * StringUtils and Notification constructor changes

    * Notification constructor changed to NotificationManager

    * Notification constructor changed to NotificationManager

    * Fix for deprecated java.net.URL(String) & FilenameIndex.getVirtualFilesByName

    * Upgraded to latest java wrapper version

    * Used simplified FilenameIndex API without case sensitivity flag

    ---------

    Co-authored-by: Aniket Shinde <[email protected]>

commit e2f30af
Merge: 36b0d7b 51c99a7
Author: Anurag Dalke <[email protected]>
Date:   Fri Aug 29 15:13:13 2025 +0530

    Merge pull request #345 from Checkmarx/other/update_java_wrapper_2.4.9

    Update AST CLI Java Wrapper to version 2.4.9

commit 51c99a7
Author: github-actions <[email protected]>
Date:   Fri Aug 29 07:58:40 2025 +0000

    Update AST CLI Java Wrapper to version 2.4.9
A
Merge branch 'customProblemWindow' into feature/agentic_ai
@gitguardian
Copy link

gitguardian bot commented Nov 26, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
21467792 Triggered Generic Password 26f7b16 src/main/java/com/checkmarx/intellij/realtimeScanners/customProblemWindow/VulnerabilityToolWindow.java View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@cx-dhanashree-wani cx-dhanashree-wani removed the request for review from cx-anurag-dalke November 27, 2025 10:58
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.

5 participants