Skip to content

ci: ignore unfixable website uuid advisory in Dependabot#278

Merged
frbrkoala merged 1 commit into
mainfrom
chore/dependabot-ignore-website-uuid
Jul 6, 2026
Merged

ci: ignore unfixable website uuid advisory in Dependabot#278
frbrkoala merged 1 commit into
mainfrom
chore/dependabot-ignore-website-uuid

Conversation

@frbrkoala

@frbrkoala frbrkoala commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

The uuid advisory in /website is reachable only through webpack-dev-server -> sockjs (the dev server behind docusaurus start), which is not part of the shipped docusaurus build output. sockjs pins uuid ^8.3.2 and the lowest non-vulnerable uuid is 14.0.0, so Dependabot's security update fails with security_update_not_possible on every run.

Ignore uuid for the /website npm ecosystem to stop the failing runs. The existing alert should be dismissed separately (dev/build-only, not exploitable in the deployed site). Revisit when Docusaurus / webpack-dev-server move off the vulnerable uuid.

What does this PR do?

🛑 Please open an issue first to discuss any significant work and flesh out details/direction — we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • New blueprint (adding a new protocol — see checklist below)
  • Documentation update
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Testing

  • I have run npm run build successfully
  • I have run npm run test and all tests pass
  • I have run npx cdk synth with a sample .env (e.g. from blueprints/dummy/samples/) and it succeeds
  • I have run pre-commit hooks: npm run run-pre-commit

New Blueprint Checklist (if adding a protocol)

  • Blueprint follows the structure of blueprints/dummy/ (reference implementation)
  • Blueprint README follows the standard template (matches Dummy section titles and ordering)
  • Setup section points to Getting Started (not inline instructions)
  • Deployment section leads with AI-driven deployment (Option 1) and manual as Option 2
  • Sample .env files are provided for at least one network (mainnet or testnet)
  • Configuration scripts follow the install/run dispatch pattern (see blueprints/dummy/)
  • Blueprint page added to website/docs/blueprints/ (.mdx mirror importing README)
  • Client Release Channels table added to README under Additional Resources

Documentation

  • I have updated relevant documentation (if applicable)
  • I have run cd website && npm run build with no broken links (if docs changed)

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The uuid advisory in /website is reachable only through
webpack-dev-server -> sockjs (the dev server behind `docusaurus start`), which
is not part of the shipped `docusaurus build` output. sockjs pins uuid ^8.3.2
and the lowest non-vulnerable uuid is 14.0.0, so Dependabot's security update
fails with security_update_not_possible on every run.

Ignore uuid for the /website npm ecosystem to stop the failing runs. The
existing alert should be dismissed separately (dev/build-only, not exploitable
in the deployed site). Revisit when Docusaurus / webpack-dev-server move off
the vulnerable uuid.
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown

Scan for commit: 44a260c | Updated: 2026-07-06 05:53:04 UTC

🔒 Security Scan Results

Scanned files: 1

⚠️ Security findings detected. Please review and address before merging.

@frbrkoala frbrkoala merged commit dfa2209 into main Jul 6, 2026
7 checks passed
@frbrkoala frbrkoala deleted the chore/dependabot-ignore-website-uuid branch July 6, 2026 06:11
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.

2 participants