chore: resolve transitive npm audit advisories#23
chore: resolve transitive npm audit advisories#23cybercraftsolutionsllc wants to merge 2 commits into
Conversation
|
Thanks for this, genuinely useful work. We've put a funded $10 TaskBounty bounty on the underlying issue: https://www.task-bounty.com/task/taskbounty-mcp-server-17-resolve-3-moderate-npm-au-nw89of . To claim it, register at https://www.task-bounty.com/, then submit your fix through the platform (REST API, MCP server, or the patch-upload endpoint). It runs against the repo's own tests in an isolated sandbox, and on a verified pass you're paid through escrow in USDC, ETH, BTC, or bank. We keep payment on-platform so it stays verified and auditable for everyone. First verified submission wins it. |
|
TaskBounty retry follow-up: I pushed a regression-test update for the verifier failure. What changed:
Validation after the push:
This should address TaskBounty's |
Fixes #17.
Summary:
Validation:
Note: I validated with tsc directly because this repo's existing npm build script ends with Unix chmod, which is not available in this Windows shell. No SDK major bump appears necessary; the lockfile refresh resolves the vulnerable transitive versions within the current @modelcontextprotocol/sdk range.
Payout route if needed: 0xB34D185318b34ec2F9E060F662Cc7feA3180049c