GQL-143 Resolve Snyk Vulnerabilities Feb 2026

[william-valencia]

Overview

What is the feature?

cmr-graphql package is being flagged as a snyk vulnerability

What is the Solution?

Moving eslint dependencies to dev dependencies. Also did an 'npm audit fix'

What areas of the application does this impact?

package.json and package-lock.json

Testing

Reproduction steps

• Environment for testing:
• Collection to test with:

Check https://app.snyk.io/org/esdis-cumulus-core-gibs-cmr-etc./project/d39edb4e-2801-4809-ab11-67a705f0b3d6/pr-check/5e362bd1-f240-44a4-ac9d-7c435623d660
Make sure the cmr-graphql package is not flagged as malicious

Attachments

Please include relevant screenshots or files that would be helpful in reviewing and verifying this change.

Checklist

• I have added automated tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (0120187) to head (6efa612).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #180   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          115       115           
  Lines         2706      2706           
  Branches       330       330           
=========================================
  Hits          2706      2706           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.