[cs-raj]

Problem

Snyk reported 4 issues in the committed lock file, all in runtime dependencies that come in through @contentstack/webhook-listener: qs 6.15.3 (3 issues, one of them high) and body-parser 2.3.0 (1 high). npm audit reported 37 findings.

Fix

• Regenerated package-lock.json within the existing ranges. qs 6.16.1 and body-parser 2.4.0 clear all 4 Snyk issues. No dependency changes in package.json, no overrides, no major upgrades.
• Bumped the package version from 0.0.8 to 0.0.9, which the version-bump check requires.
• DataSync projects install this package as a dependency and resolve webhook-listener's ranges themselves. Those ranges already allow the fixed qs and body-parser, so a fresh install picks them up.
• .talismanrc: the package-lock.json checksum entry is replaced by an entry that ignores the lock file's integrity hashes, because a checksum stops matching every time the lock file is regenerated.

Still open (npm audit, 33): 32 are the npm 8 dev dependency and the packages it bundles (tar, pacote, cacache, ip, the libnpm* packages and others). They are dev-only and need npm 12, a major. The last one is a low finding in aws-sdk v2, which has no fixed v2 release; the fix is migrating to AWS SDK v3.

Verified: Snyk 4 → 0, npm audit 37 → 33; npm run build-ts passes with output identical to the committed dist/, and npm test passes (33 tests).

🤖 Generated with Claude Code

[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	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