[netrajpatel]

Problem

• The launch team released @contentstack/cli-launch 1.11.4; CLI v1 still shipped 1.11.3, which bundled adm-zip 0.5.18 with 8 known vulnerabilities.
• Snyk reported 24 issues on v1-legacy, several with patched versions available within existing ranges (follow-redirects, qs, body-parser, fast-uri) and csv-parse 4 via tty-table 4.

Fix

• Bump @contentstack/cli-launch to ^1.11.4 and @contentstack/cli to 1.69.1. Note: launch 1.11.4 depends on the v2 core (cli-command/cli-utilities 2.0.2), so v1 now carries both cores. Both read the same config store, so login and region are shared; all launch commands load.
• Move follow-redirects (1.16.2), qs (6.16.2) and body-parser (1.20.9) to patched in-range versions, and raise the fast-uri pin from 4.2.1 to 4.2.3.
• Upgrade tty-table 4 → 7 in cli-utilities (version 1.20.2) and pin it workspace-wide, so the published cli-utilities used by bundled plugins gets it too. This removes csv-parse 4. The default export and Header type are unchanged; tables render the same.
• Ignore SNYK-JS-PICOMATCH-21248802 until 2026-11-29: picomatch 4.0.7 is the latest release, so no fix exists. Snyk reads .snyk per workspace package, so each package has a copy. The two existing (expired) tmp ignores are kept.
• Snyk: 24 → 4 remaining, none with a fix available (adm-zip 0.6.1, deepmerge via launch; yarn, npm license via @oclif/plugin-plugins).

Testing

• pnpm run setup (clean install + build) passes; all unit tests pass (277).
• csdx --version → 1.69.1; launch, launch:functions, launch:logs, launch:open, launch:environments, launch:deployments help all load.
• Not yet tested: a real csdx launch deploy.

Known, not in this PR: --csv table output calls papaparse's parse instead of unparse and crashes (pre-existing since April 2025).

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	0	25	✅ Passed
🟡 Medium Severity	0	4	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	1	90 / 365 days	⚠️ Warning
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 0
• Medium without fixes: 4
• Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	0	25	✅ Passed
🟡 Medium Severity	0	0	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	0	90 / 365 days	✅ Passed
🔵 Low	0	0	180 / 365 days	✅ Passed

✅ BUILD PASSED - All security checks passed

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	0	25	✅ Passed
🟡 Medium Severity	0	48	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	1	90 / 365 days	⚠️ Warning
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 0
• Medium without fixes: 48
• Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.