Fix the chore actions

[TingDaoK]

LLM have successfully fixed the issue in the dependency-updates.yml file where the script was failing when packages don't have all the expected fields in the audit results. The specific problem you encountered with the jest-dev-server package has been resolved.

Root Cause Analysis

The script was failing with exit code 5 because:

1. fixAvailable field was an object instead of a boolean: In the jest-dev-server case, fixAvailable was {"name": "jest-puppeteer", "version": "11.0.0", "isSemVerMajor": true} instead of a simple true/false
2. via field contained strings instead of objects: The via array contained ["wait-on"] (strings) instead of objects with title, url, and cvss properties
3. The script tried to access .title and .url on strings, which caused jq to fail

Fixes Applied

1. Fixed fixAvailable handling:

Before:

FIX_AVAILABLE=$(jq -r ".vulnerabilities[\"$PACKAGE\"].fixAvailable // false" audit_results.json 2>/dev/null)

After:

FIX_AVAILABLE=$(jq -r "if .vulnerabilities[\"$PACKAGE\"].fixAvailable then (if (.vulnerabilities[\"$PACKAGE\"].fixAvailable | type) == \"object\" then \"true\" else (.vulnerabilities[\"$PACKAGE\"].fixAvailable | tostring) end) else \"false\" end" audit_results.json 2>/dev/null)

2. Fixed via field processing:

Before: Always tried to access .title, .url, and .cvss.score properties

After: Added type checking to handle both cases:

• Objects: Process as before with title, url, and cvss.score
• Strings: Display as "Vulnerability via package: [package-name]"
• Missing/null: Display "No advisory details available"

3. Enhanced error handling:

All jq commands now use the // "default_value" syntax to provide fallback values when fields are missing.

Verification

I created comprehensive tests that verified the fixes work correctly with:

• ✅ jest-dev-server case: fixAvailable as object, via as strings
• ✅ Normal case: fixAvailable as boolean, via as objects
• ✅ Missing fields case: Non-existent packages with no data
• ✅ Mixed scenarios: Different combinations of field types

Result

The dependency-updates workflow will now:

• Continue execution gracefully when packages have incomplete vulnerability data
• Properly handle both object and boolean fixAvailable values
• Process both string and object via arrays appropriately
• Provide meaningful default values instead of failing with exit code 5

The script is now robust against the variability in npm audit output formats and will no longer fail on packages like jest-dev-server that have non-standard field structures.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.