Sonarcloud security updating

SonarCloud Security Updating Skill

This skill applies triage decisions to SonarCloud security issues (vulnerabilities and hotspots) by reading JSON or CSV files with review decisions and updating the statuses in SonarCloud via the API.

Prerequisites

• Node.js v18 or higher
• SonarCloud API token with Administer Security Hotspots and Administer Issues permissions
• JSON file with triage decisions (RECOMMENDED) - output from sonarcloud-security-triaging skill
  • Or CSV file with triage columns (legacy format)

Workflow

This skill complements the export and triage skills:

JSON Workflow (Recommended)

1. Export → sonarcloud-security-exporting generates JSON with rich data
2. Triage → sonarcloud-security-triaging populates triage fields
3. Apply → This skill reads triage decisions from JSON and updates SonarCloud

CSV Workflow (Legacy)

1. Export → sonarcloud-security-exporting generates CSV
2. Review → User adds triage columns in spreadsheet (Action, Resolution, Comment, Reviewer)
3. Apply → This skill reads CSV and updates SonarCloud

Input Formats

JSON Format (Recommended)

The JSON file should contain issues with populated triage fields (output from sonarcloud-security-triaging skill):

{
  "exportMetadata": { ... },
  "issues": [
    {
      "key": "AZPV1fTprahIrD-njDRb",
      "project": "NASA-PDS_doi-ui",
      "type": "SECURITY_HOTSPOT",
      "url": "https://sonarcloud.io/...",
      "triage": {
        "action": "REVIEWED",
        "resolution": "SAFE",
        "comment": "This is a namespace URI, not an HTTP connection",
        "reviewer": "claude-code",
        "confidence": "HIGH"
      }
    },
    {
      "key": "AZnP1S0b_yFrdYV3Iu6e",
      "project": "NASA-PDS_data-upload",
      "type": "VULNERABILITY",
      "url": "https://sonarcloud.io/...",
      "triage": {
        "action": "wontfix",
        "comment": "Scheduled for future sprint",
        "reviewer": "claude-code"
      }
    }
  ]
}

What gets applied:

• Issues with triage field populated (not null) are processed
• action, resolution, and comment from triage object
• Issue key used directly (no URL parsing needed)

CSV Format (Legacy)

The CSV must have these columns (export + 4 triage columns):

Original columns:

• Project, Type, Severity, Status, Rule, Message, Component, Line, Created, URL

Added triage columns:

• Action - For SECURITY_HOTSPOT: REVIEWED | For VULNERABILITY: confirm, falsepositive, wontfix, resolve
• Resolution - For SECURITY_HOTSPOT only: SAFE or FIXED
• Comment - Review explanation (optional but recommended)
• Reviewer - Email or name of reviewer (optional, for tracking)

Example:

Project,Type,Severity,Status,Rule,Message,Component,Line,Created,URL,Action,Resolution,Comment,Reviewer
NASA-PDS_doi-ui,SECURITY_HOTSPOT,,TO_REVIEW,,Using http protocol...,src/file.jsx,119,2021-01-28T19:38:04+0000,https://sonarcloud.io/.../hotspots=AZPV1fTprahIrD-njDRb,REVIEWED,SAFE,"URI not URL",[email protected]
NASA-PDS_data-upload,VULNERABILITY,MAJOR,OPEN,python:S7608,Add ExpectedBucketOwner...,src/sync.py,134,2025-10-10T20:33:50+0000,https://sonarcloud.io/.../open=AZnP1S0b_yFrdYV3Iu6e&...,wontfix,,"Scheduled for future sprint",[email protected]

Execution Steps

Step 1: Check Prerequisites

Verify the SonarCloud token is set:

env | grep SONARCLOUD_TOKEN

If not set, prompt the user to set it (same token used for audit skill).

Step 2: Validate Input File

For JSON: Check that the file exists and has valid structure:

• Must have issues array
• Issues should have triage field populated (not null)
• Issues with triage.action will be processed

For CSV: Check that the file exists and has required columns:

• Must have URL column (to extract issue/hotspot keys)
• Must have Action column (identifies rows to process)
• For SECURITY_HOTSPOT rows with Action=REVIEWED, must have Resolution column

Step 3: Run the Update Script

Execute the script (auto-detects format):

JSON Input

cd sonarcloud-security-updating
node scripts/apply-triage.mjs <path-to-triaged.json> [--dry-run]

CSV Input

cd sonarcloud-security-updating
node scripts/apply-triage.mjs <path-to-triaged.csv> [--dry-run]

Parameters:

• <path-to-file> (required): Path to JSON or CSV file with triage decisions
• --dry-run (optional): Preview changes without actually updating SonarCloud

Format detection: Automatic based on file extension (.json or .csv) or content inspection

The script will:

For JSON input:

1. Parse the JSON file
2. Filter issues where triage is not null and triage.action is set
3. Use issue key directly (no URL parsing)
4. For each issue:
   • SECURITY_HOTSPOT → Call POST /api/hotspots/change_status
     • Parameters: hotspot=key, status=REVIEWED, resolution=triage.resolution, comment=triage.comment
   • VULNERABILITY → Call POST /api/issues/do_transition
     • Parameters: issue=key, transition=triage.action, comment=triage.comment

For CSV input:

1. Parse the CSV file
2. Filter rows where Action column is not empty
3. Extract issue/hotspot key from the URL column
4. For each row:
   • SECURITY_HOTSPOT → Call POST /api/hotspots/change_status
     • Parameters: hotspot, status=REVIEWED, resolution (SAFE/FIXED), comment
   • VULNERABILITY → Call POST /api/issues/do_transition
     • Parameters: issue, transition (confirm/falsepositive/wontfix/resolve), comment
5. Log success/failure for each update
6. Generate summary report

Step 4: Review Results

The script outputs:

• Success count: Number of issues successfully updated
• Failed count: Number of issues that failed to update (with error messages)
• Skipped count: Number of rows skipped (empty Action or already in target status)
• Summary CSV: Optional output file with status of each update

Step 5: Verify in SonarCloud

After running, verify a few updates in the SonarCloud UI:

• Navigate to the project's Security Hotspots or Issues page
• Check that statuses were updated correctly
• Verify comments were added

API Endpoints Used

For Security Hotspots (TO_REVIEW → REVIEWED)

Endpoint: POST /api/hotspots/change_status

Parameters:

• hotspot (required): Hotspot key extracted from URL (e.g., AZPV1fTprahIrD-njDRb)
• status (required): Always REVIEWED
• resolution (required): SAFE or FIXED
• comment (optional): Review explanation

Example:

curl -X POST 'https://sonarcloud.io/api/hotspots/change_status' \
  -H 'Authorization: Bearer <token>' \
  -d 'hotspot=AZPV1fTprahIrD-njDRb' \
  -d 'status=REVIEWED' \
  -d 'resolution=SAFE' \
  -d 'comment=False positive. This is a URI not a URL.'

For Vulnerabilities (OPEN → Other statuses)

Endpoint: POST /api/issues/do_transition

Parameters:

• issue (required): Issue key extracted from URL (e.g., AZnP1S0b_yFrdYV3Iu6e)
• transition (required): One of confirm, falsepositive, wontfix, resolve
• comment (optional): Explanation for the transition

Example:

curl -X POST 'https://sonarcloud.io/api/issues/do_transition' \
  -H 'Authorization: Bearer <token>' \
  -d 'issue=AZnP1S0b_yFrdYV3Iu6e' \
  -d 'transition=wontfix' \
  -d 'comment=Scheduled for future sprint'

Extracting Keys from URLs

The script extracts issue/hotspot keys from the URL column:

Security Hotspot URL:

https://sonarcloud.io/project/security_hotspots?id=NASA-PDS_doi-ui&hotspots=AZPV1fTprahIrD-njDRb
                                                                              ^^^^^^^^^^^^^^^^^^^^^^
                                                                              Extract this part

Vulnerability URL:

https://sonarcloud.io/project/issues?open=AZnP1S0b_yFrdYV3Iu6e&id=NASA-PDS_data-upload
                                           ^^^^^^^^^^^^^^^^^^^^^
                                           Extract this part

Error Handling

Authentication Errors (401)

• Token is invalid or expired
• Token doesn't have required permissions
• Regenerate token with correct permissions

Permission Errors (403)

• Token doesn't have Administer Security Hotspots permission for hotspots
• Token doesn't have Administer Issues permission for vulnerabilities
• Check token scopes in SonarCloud settings

Not Found Errors (404)

• Issue/hotspot key is invalid or was deleted
• Skip and continue with next item

Invalid Transition Errors (400)

• Transition not allowed from current status
• Resolution required but not provided
• Log error and skip item

Rate Limiting (429)

• Script automatically waits 60 seconds and retries
• If persistent, reduce batch size or run during off-peak hours

Dry Run Mode

Before applying changes, use --dry-run to preview:

JSON:

node scripts/apply-triage.mjs issues-triaged.json --dry-run

CSV:

node scripts/apply-triage.mjs triage.csv --dry-run

Dry run output:

[DRY RUN] Would update hotspot AZPV1fTprahIrD-njDRb:
  Project: NASA-PDS_doi-ui
  Type: SECURITY_HOTSPOT
  Action: Change status to REVIEWED (SAFE)
  Comment: "False positive. This is a URI not a URL."

[DRY RUN] Would update issue AZnP1S0b_yFrdYV3Iu6e:
  Project: NASA-PDS_data-upload
  Type: VULNERABILITY
  Action: Transition to wontfix
  Comment: "Scheduled for future sprint"

Summary: 2 updates would be applied (0 errors)

Best Practices

1. Always run dry-run first to preview changes
2. Add meaningful comments to explain triage decisions (helps future reviewers)
3. Start small - test with 5-10 issues before processing thousands
4. Track reviewer - include email/name for accountability (JSON: triage.reviewer, CSV: Reviewer column)
5. Backup original - keep original export before adding triage decisions
6. Verify sample - Check a few issues in SonarCloud UI after bulk update
7. Use JSON when possible - Cleaner workflow, no URL parsing errors, full traceability

Troubleshooting

JSON Format Issues

"No issues with triage decisions found"

• All triage fields are null
• Run sonarcloud-security-triaging skill first to populate triage decisions

"Invalid triage action"

• triage.action must be valid for the issue type
• SECURITY_HOTSPOT: action=REVIEWED, resolution=SAFE|FIXED
• VULNERABILITY: action=confirm|falsepositive|wontfix|resolve

"JSON parse error"

• File is corrupted or not valid JSON
• Use jq '.' file.json to validate JSON syntax

CSV Format Issues

"Column 'Action' not found"

• CSV is missing the Action column
• Ensure you added the 4 triage columns: Action, Resolution, Comment, Reviewer

"Could not extract hotspot key from URL"

• URL format may have changed
• Verify URL column contains valid SonarCloud URLs
• Check if URL contains hotspots= or open= parameter
• Solution: Use JSON format instead (no URL parsing needed)

"No rows to process"

• All Action columns are empty
• Add triage decisions to at least one row

"Invalid resolution: must be SAFE or FIXED"

• For SECURITY_HOTSPOT with Action=REVIEWED, Resolution must be SAFE or FIXED
• Check spelling and capitalization

Example Workflows

JSON Workflow (Recommended - Fast & Automated)

1. Export security issues

cd sonarcloud-security-exporting
node scripts/fetch-security-issues.mjs nasa-pds issues.json --format json --include-snippets

Output: issues.json with code context and rule details

2. Analyze and suggest triage decisions

# Use sonarcloud-security-triaging skill
# Claude reads issues.json, analyzes code context, suggests decisions
# Output: issues-triaged.json with populated triage fields

3. Dry run to preview

cd sonarcloud-security-updating
node scripts/apply-triage.mjs ../issues-triaged.json --dry-run

4. Apply triage decisions

node scripts/apply-triage.mjs ../issues-triaged.json

5. Verify in SonarCloud

• Open a few updated issues in SonarCloud UI
• Confirm status changes and comments appear correctly

Total time: ~15-30 minutes for thousands of issues (mostly automated)

---

CSV Workflow (Legacy - Manual Review)

1. Export security issues

cd sonarcloud-security-exporting
node scripts/fetch-security-issues.mjs nasa-pds security-audit.csv

2. Review and add triage columns

Open security-audit.csv in Excel/Google Sheets and add 4 columns:

Action	Resolution	Comment	Reviewer
REVIEWED	SAFE	False positive. Uses URI not URL.	[email protected]
wontfix		Low priority. Scheduled for Q2.	[email protected]

Save as security-triage.csv

3. Dry run to preview

cd sonarcloud-security-updating
node scripts/apply-triage.mjs ../security-triage.csv --dry-run

4. Apply triage decisions

node scripts/apply-triage.mjs ../security-triage.csv

5. Verify in SonarCloud

• Open a few updated issues in SonarCloud UI
• Confirm status changes and comments appear correctly

Total time: Several hours to days (manual spreadsheet review, URL parsing)

Output

Console output:

🔧 SonarCloud Security Triage

Input file: security-triage.csv
Dry run: NO
Total rows: 4647
Rows with triage decisions: 127

Processing...
[1/127] ✅ Hotspot AZPV1fTprahIrD-njDRb → REVIEWED (SAFE)
[2/127] ✅ Issue AZnP1S0b_yFrdYV3Iu6e → wontfix
[3/127] ⚠️  Hotspot ABC123 → 404 Not Found (skipped)
...

📊 Summary:
   ✅ Successfully updated: 125
   ❌ Failed: 1
   ⏭️  Skipped: 1

Failed updates:
- Row 45: Hotspot XYZ789 - 403 Forbidden (insufficient permissions)

All done!

Notes

• Only rows with non-empty Action column are processed
• Empty Action = no update (useful for keeping already-reviewed items in the CSV)
• The Reviewer column is for tracking purposes only (not sent to SonarCloud)
• Comments in SonarCloud will show timestamp and API user (token owner), not the Reviewer value
• Updates are applied sequentially with small delays to respect rate limits
• Script is idempotent: running twice won't cause issues (SonarCloud will reject invalid transitions)