Skip to content
This repository was archived by the owner on Apr 21, 2026. It is now read-only.

fix(deps): bump @forgespace/branding-mcp to ^0.56.0#47

Merged
LucasSantana-Dev merged 1 commit into
mainfrom
fix/branding-mcp-bump
Apr 7, 2026
Merged

fix(deps): bump @forgespace/branding-mcp to ^0.56.0#47
LucasSantana-Dev merged 1 commit into
mainfrom
fix/branding-mcp-bump

Conversation

@LucasSantana-Dev

Copy link
Copy Markdown
Member

Summary

Closes Dependabot alert #22 (@anthropic-ai/sdk 0.79.0 — Memory Tool Path Validation sandbox escape, medium severity).

brand-guide doesn't depend on @anthropic-ai/sdk directly; the vulnerable version came in transitively through @forgespace/branding-mcp@^0.55.3. @forgespace/branding-mcp 0.56.0 already pins @anthropic-ai/sdk@^0.82.0, so bumping the dep range closes the alert with no other changes:

brand-guide (^0.55.3 -> ^0.56.0)
  -> branding-mcp 0.56.0
    -> @anthropic-ai/sdk 0.82.0  (patched)

Test plan

  • npm install — lockfile resolved cleanly
  • npm run build:lib — green
  • npm test — 24/24 pass
  • npm run api:check — green (confirms the 12 re-exported types are unchanged between branding-mcp 0.55.3 and 0.56.0, so this is non-breaking for downstream consumers)

Closes Dependabot alert #22 (medium severity).

Transitive vulnerability in @anthropic-ai/sdk 0.79.0 — Memory Tool
Path Validation allows sandbox escape (GHSA, fixed in 0.81.0).
brand-guide cannot bump @anthropic-ai/sdk directly because it does
not depend on it; the SDK comes through @forgespace/branding-mcp.

@forgespace/branding-mcp 0.56.0 already pins @anthropic-ai/sdk
^0.82.0, so the chain becomes:

  brand-guide (^0.55.3 -> ^0.56.0)
    -> branding-mcp 0.56.0
      -> @anthropic-ai/sdk 0.82.0  (patched)

api:check confirms the 12 re-exported types from branding-mcp are
unchanged between 0.55.3 and 0.56.0, so this is non-breaking for
brand-guide consumers.
@coderabbitai

coderabbitai Bot commented Apr 7, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@LucasSantana-Dev has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 13 minutes and 2 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 13 minutes and 2 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7afda135-3485-41e1-b359-3fd9167ef5eb

📥 Commits

Reviewing files that changed from the base of the PR and between 6363016 and 01c40fe.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/branding-mcp-bump

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sonarqubecloud

sonarqubecloud Bot commented Apr 7, 2026

Copy link
Copy Markdown

@LucasSantana-Dev LucasSantana-Dev merged commit 04fb422 into main Apr 7, 2026
16 checks passed
@LucasSantana-Dev LucasSantana-Dev deleted the fix/branding-mcp-bump branch April 7, 2026 22:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant