Repository navigation
Conversation
…tall ggshield in release workflow (IS-7341)
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
🟠 High Severity - SLA Breached Issues (with fixes)Showing 6 issue(s) that have exceeded the 30-day SLA threshold:
🟡 Medium Severity - SLA Breached Issues (with fixes)Showing 10 issue(s) that have exceeded the 90-day SLA threshold:
ℹ️ 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:
❌ BUILD FAILED - Security checks failed Please review and fix the security vulnerabilities before merging. |
Adds a GitGuardian scan at the npm postpack stage so the exact tarball being published is scanned. Existing postpack scripts are preserved (scan chained in front). All publish jobs install ggshield and pass GITGUARDIAN_API_KEY. Blocking: a detected secret fails the publish. Validated locally (clean pack exits 0; a planted secret in the published output exits 1). Same pattern as cli #2737, types-generator, contentstack-management-javascript. Requires repo/org secret GITGUARDIAN_API_KEY before the next release. IS-7341