Skip to content

GitGuardian secret scan on package publish (blocking) - #211

Merged
alok-cstk merged 1 commit into
mainfrom
feat/gitguardian-publish-scan
Oct 21, 2026
Merged

alok-cstk merged 1 commit into
mainfrom
feat/gitguardian-publish-scan

Conversation

@alok-cstk

Copy link
Copy Markdown
Contributor

Adds a GitGuardian secret scan at the npm postpack stage so the exact tarball being published is scanned for secrets. The hook runs ggshield secret scan archive ./*.tgz after pack; a detected secret fails the publish (blocking). Both release jobs (npmjs and GitHub registry) install ggshield via pipx and pass the GITGUARDIAN_API_KEY service-account token.

Validated locally: a secret placed in the bundled output (dist) blocks the pack (exit 1); a clean pack passes (exit 0).

Scope note: this scans the published bundle (tsup output), so it catches secrets in shipped code. Secrets in source files that aren’t bundled into dist are out of scope here by design and remain covered by the org-level GitGuardian PR scan.

…tall ggshield in release workflow; ignore ggshield cache (IS-7341)
@alok-cstk
alok-cstk requested review from a team as code owners October 21, 2026 08:45
@snyk-io

snyk-io Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

✅ 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

Copy link
Copy Markdown

🔒 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 4 25 ✅ Passed
🟡 Medium Severity 0 5 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

ℹ️ 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: 4
  • Medium without fixes: 5
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@alok-cstk
alok-cstk merged commit 6a2ead7 into main Oct 21, 2026
7 checks passed
@alok-cstk
alok-cstk deleted the feat/gitguardian-publish-scan branch October 21, 2026 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants