[failproofai-legion-901] Combine the open Dependabot PRs and clear every fixable security finding

[NiveditJain]

One PR for the fifteen open Dependabot PRs, plus the security fixes neither Dependabot nor the gate could get to. The OSV-Scanner gate has been red on main's daily scan with 20 fixable advisories. After this PR, CI's own scanner image reports No issues found.

What's in it

Thirteen Dependabot commits, cherry-picked unchanged:

PR	Update
#887, #886	next, eslint-config-next 16.3.6 → 16.4.0
#892	eslint 10.11.0 → 10.12.0
#893	@anthropic-ai/sdk 0.128.0 → 0.133.0
#891	@types/node 26.6.2 → 26.6.5
#895	lucide-react 1.48.0 → 1.55.0
#894	@tanstack/react-virtual 3.14.13 → 3.14.14
#890	@vitejs/plugin-react 6.1.1 → 6.1.2
#888	jsdom 30.1.1 → 30.1.2
#889	posthog-node 5.54.1 → 5.55.1
#896	Rust group: serde_json 1.0.152, libc 0.2.190, tokio 1.53.2, getrandom 0.4.3, tokio-rustls 0.26.6, proptest 1.12.0
#897	fp-cloud-cli: typer 0.27.3, posthog 7.67.0
#898	sdk/python: langchain-core 1.6.9, langgraph 1.2.14, crewai 1.15.27, pydantic-ai-slim 2.54.0

#883 is covered without its own commit. #898 already takes langgraph-sdk to 0.4.7, past #883's 0.4.4. The cherry-pick conflicted on that one line and was skipped.

The eleven findings no Dependabot PR covered. The bumps above close nine of the twenty (next ×6, pydantic-ai-slim ×2, langgraph-sdk). The other eleven are transitive or held by an override:

Lockfile	Fix	Advisories
sdk/python/uv.lock	banks 2.5.0 → 2.5.1, multidict 6.7.1 → 6.9.1 (uv lock --upgrade-package)	GHSA-556j-vv39-8rqv, GHSA-54p9-h82j-f925
Cargo.lock	quinn-proto 0.11.16 → 0.11.19, ruzstd 0.9.0 → 0.9.1 (cargo update -p; no other edge moves)	RUSTSEC-2026-0338…0342, RUSTSEC-2026-0344
bun.lock	sharp override 0.35.4 → 0.35.5 (libvips 1.3.3 → 1.3.4)	GHSA-wq5f-xc86-pv6w
bun.lock, sdk/typescript/package-lock.json	source-map-js 1.2.1 → 1.2.2 (in range of every ^1.2.1)	GHSA-68fv-2mgg-jv7q

• sharp stays an override, as [docs] Add the Reo.dev beacon to the documentation site #790 left it. next 16.4.0 still asks for ^0.35.4. 0.35.5 loads against libvips 8.18.7 and round-trips a PNG encode.
• bun.lock was edited entry by entry, not regenerated. Any bun install over an edited lock re-resolved about 100 unrelated packages. bun install --frozen-lockfile accepts the result, and a plain bun install reports no changes.
• chromadb moved 1.1.1 → 1.5.9. crewai 1.15.27 requires chromadb~=1.5.9. That is the newest release and is still inside all four advisories' ranges. The four osv-scanner.toml ignores stay, and their text now names the version actually locked.

Published after the first CI run. RUSTSEC-2026-0346 through RUSTSEC-2026-0349 landed overnight, against rustls 0.23.45, the TLS stack compiled into failproofaid through reqwest. All four are fixed in 0.23.46. cargo update -p rustls moves only that crate.

GitHub's Dependabot alerts (11 open)

There are no code-scanning analyses on this repo, and secret scanning is off, so the Dependabot alerts are the whole list.

Alert	Package	Outcome
#47	langgraph-sdk (sdk/python)	Fixed, 0.4.7
#48	@modelcontextprotocol/client (mastra-1 fixture)	Fixed, override to 2.2.0; see below
#1–#4	chromadb	No fixed release exists (1.5.9 is the newest). Ignored in osv-scanner.toml until 2026-11-20
#5	nltk	No fixed release exists (3.10.3 is the newest). Same
#7, #9, #33, #41	ai@4.3.19, @ai-sdk/provider-utils@2.2.8 (ai-4, mastra-0 fixtures)	Accepted in SECURITY.md: the only fix is the major these fixtures exist to stay below

#48, and why #884 is closed without being merged. @mastra/mcp@2.0.0 pins @modelcontextprotocol/client exactly at 2.0.0. #884 moved @mastra/mcp to 2.3.0 to reach the fix, but 2.3.0 peers on @mastra/core >=1.75.0-0, which cannot install next to the fixture's @mastra/core@1.68.0. This PR applies SECURITY.md's case 1 instead: a fixture-local overrides entry for 2.2.0, re-resolved with npm install --package-lock-only --ignore-scripts. The client now carries its own @modelcontextprotocol/core@2.2.0, and every pin resolves as before. The rest of #884 moves ai from 4.3.19 to 5.0.52 in ai-4 and mastra-0. SECURITY.md names that move as never the answer, and it was why #884's integration shards were red.

Verified locally

Every check reproduced the CI job's own commands:

• Supply Chain: ghcr.io/google/osv-scanner-action:v2.5.0 with the workflow's scan-args reports No issues found, exit 0. All six ignores are still used.
• quality: lint passes (0 errors) and tsc --noEmit passes.
• test: bun run test:run passes 7785 tests in each of the three env configs. One existing flake (jev-activity-row.test.tsx) failed once in default and then passed 5/5 in isolation. It failed all three attempts on chore(deps): bump the npm_and_yarn group across 3 directories with 3 updates #884, which touched none of the root dependencies.
• build and test-e2e: bun run build passes (Next 16.4.0); e2e passes 327 tests.
• rust-quality: cargo fmt --check, cargo clippy -D warnings and cargo test --workspace pass (744 tests).
• Python: fp-cloud-cli passes on 3.10–3.13, failproofai-sdk on 3.10–3.14, and the framework-adapter integrations with every extra installed.
• failproofai-ts-sdk: typecheck, lint, build and tests pass. The mastra integration suites pass against mastra-0 and mastra-1, including the mcp and mcp-toolsets scenarios that drive MCPClient through the overridden client.
• failproofai-ts-sdk-integrations (runtimes): the whole shard passes, 1132 tests under Node, Bun and Deno. On the first CI run this job failed for infrastructure reasons: a registry ECONNRESET during a fixture npm ci, then "The runner has received a shutdown signal" during the retry. It runs again on the rustls push.

Supersedes #883, #884, #886, #887, #888, #889, #890, #891, #892, #893, #894, #895, #896, #897, #898. Each one is closed with a link here.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Y58bUoeFUPGfG6zL8vnZAf

Hermes review

Field	Value
Status	Approved
Reviewed commit	201f6f4c9f30601e717c67b23196d0cf5b18ed95
Policy revision	1d8f31d926828f3bae215c58f5b35baa44acbff0
Model	gpt-5.6-terra
Duration	286s
Updated	2026-10-14T21:05:28.398846058+00:00

Summary

No actionable correctness, compatibility, security-boundary, data-safety, or operability defects found in the reviewed dependency and lockfile updates.

Changes

• Updated root JavaScript, Rust, and Python dependency resolutions to address security advisories.
• Added a fixture-local npm override resolving the Mastra MCP client to 2.2.0 while retaining the fixture's Mastra pins.
• Updated OSV advisory exception documentation for the new chromadb resolution and release notes.

Validation

• Passed docker run --rm --network=none node:22-bookworm-slim node -e '<parse changed package JSON and verify MCP override lock entries>' — Changed package manifests and lockfiles parsed successfully; the fixture lock resolves MCP client and its nested core to 2.2.0. (0s)
• Skipped npm ci --ignore-scripts (Mastra fixture, disposable container) — A clean install requires uncached packages from the external npm registry; the isolated harness could not complete that external-service-dependent check. No centrally configured validation commands were provided. (120s)

Findings

None.

Open questions

None.

Policy overrides

None.

Summary by CodeRabbit

• Chores
  • Updated supporting packages and development tooling, including security-related dependencies.
  • Adjusted compatibility settings for the TypeScript integration while preserving its existing core package version.
  • Updated vulnerability advisory records to reflect the supported ChromaDB version; the listed advisories and expiration dates remain unchanged.
  • Recorded remediation for fixable supply-chain advisories. Some ChromaDB advisories remain listed because no fix is available.

[github-actions]

Thanks @NiveditJain for your contribution to Failproof AI! 🙌

We'd love to discuss your PR and welcome you to our community.

Discord: https://discord.befailproof.ai/
Reddit: https://www.reddit.com/r/failproofai/

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: b4fdd4d5-8632-4df5-84f3-44ea6f587765

📥 Commits

Reviewing files that changed from the base of the PR and between a4fc98b and 201f6f4.

⛔ Files ignored due to path filters: 1

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing: 1

• CHANGELOG.md

🚧 Files skipped from review as they are similar to previous changes: 1

• CHANGELOG.md

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

📝 Walkthrough

This change updates Rust and npm dependency versions, revises chromadb advisory ignore details for version 1.5.9, and pins the MCP client to version 2.2.0 in a TypeScript integration fixture.

Changes: Dependency and advisory updates

Layer / File(s)	Summary
Dependency version updates crates/fpai-collect/Cargo.toml, package.json, CHANGELOG.md	The getrandom, @anthropic-ai/sdk, @types/node, and sharp versions change. The changelog records dependency and advisory updates.
MCP fixture override sdk/typescript/integration/fixtures/mastra-1/package.json, sdk/typescript/CHANGELOG.md	The fixture pins @modelcontextprotocol/client to 2.2.0. The changelog records the override, package resolution details, scenario test results, and lockfile update.
chromadb advisory ignores osv-scanner.toml	The four advisory reasons identify chromadb 1.5.9 and record the CrewAI version constraint. Advisory IDs and expiration dates remain unchanged.

Priority: ⬆️ High

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 201f6

No merge-blocking issue is identified; the dependency and advisory updates are mergeable after normal checks.

Pre-merge checks: 5

Passed checks: 5 passed

Check name	Status	Explanation
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Title check		The title clearly summarizes the main change: combining Dependabot updates and resolving fixable security findings.
Description check		The description provides detailed scope, security outcomes, retained exceptions, testing results, and links to superseded PRs. It does not reproduce the template's Type of Change and Checklist section…

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks each version line,
While Rust and npm dependencies align.
A fixture pins the client just so,
The advisory notes track chromadb’s flow.
Then off I hop beneath the moon,
With changelog pages tucked in tune.}

_{Comment @coderabbitai help to get the list of available commands.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​tokio@​1.53.1 ⏵ 1.53.2
	npm/​next@​16.4.0
	npm/​@​anthropic-ai/​sdk@​0.128.0 ⏵ 0.133.0			+1	+1
	npm/​eslint-config-next@​16.3.6 ⏵ 16.4.0	+1		+2
	npm/​@​tanstack/​react-virtual@​3.14.13 ⏵ 3.14.14	+1		+1	+2
	cargo/​libc@​0.2.189 ⏵ 0.2.190	-9		-7
	npm/​posthog-node@​5.54.1 ⏵ 5.55.1	+1		+1	-1
	npm/​lucide-react@​1.48.0 ⏵ 1.55.0			+1	+1
	npm/​@​types/​node@​26.6.2 ⏵ 26.6.5			+1
	cargo/​serde_json@​1.0.151 ⏵ 1.0.152
	pypi/​posthog@​7.60.1 ⏵ 7.67.0	-6
	npm/​@​vitejs/​plugin-react@​6.1.1 ⏵ 6.1.2	+1		+1	-1
	cargo/​proptest@​1.11.0 ⏵ 1.12.0
	cargo/​ruzstd@​0.9.0 ⏵ 0.9.1
	cargo/​tokio-rustls@​0.26.5 ⏵ 0.26.6
	npm/​jsdom@​30.1.1 ⏵ 30.1.2
	npm/​eslint@​10.11.0 ⏵ 10.12.0	+1			-1
	pypi/​typer@​0.27.2 ⏵ 0.27.3	+1

View full report

[hermes-exosphere]

Hermes

Status	Reviewing
Verdict	Not reviewed yet
Head	a4fc98bde05d
Rounds	0 of 5

No summary yet.

What this changes

No component map for this revision.

Rounds

No review has finished on this pull request yet.

Findings

Nothing raised yet.

---

@hermes-exosphere help lists every command. This comment is maintained in place — I rewrite it after each review rather than posting a new one.

[hermes-exosphere]

Hermes

Status	Reviewed
Verdict	Approved
Head	201f6f4c9f30
Rounds	0 of 5

No actionable correctness, compatibility, security-boundary, data-safety, or operability defects found in the reviewed dependency and lockfile updates.

What this changes

flowchart LR
    n0Rootapplicationtoolchain["~ Root application toolchain"]
    n1CollectorTLSandentropystack["~ Collector TLS and entropy stack"]
    n2PythonSDKadapterdependencies["~ Python SDK adapter dependencies"]
    n3CloudCLIdependencies["~ Cloud CLI dependencies"]
    n4Mastraintegrationfixture["~ Mastra integration fixture"]
    n5Supplychainadvisorypolicy["~ Supply-chain advisory policy"]
    n6Releasenotes["~ Release notes"]
    n0Rootapplicationtoolchain -- "resolved dependency advisories" --> n5Supplychainadvisorypolicy
    n1CollectorTLSandentropystack -- "resolved Rust advisories" --> n5Supplychainadvisorypolicy
    n2PythonSDKadapterdependencies -- "chromadb exception scope" --> n5Supplychainadvisorypolicy
    n4Mastraintegrationfixture -- "patched MCP client" --> n5Supplychainadvisorypolicy
    n4Mastraintegrationfixture -- "fixture compatibility notes" --> n6Releasenotes
    n3CloudCLIdependencies -- "dependency update notes" --> n6Releasenotes

Loading

Rounds

Round	Reviewed	Commits in this round	Verdict
0	a4fc98bde05d	20ef88d8ab46 1c7f3d21a538 df514e54a949 e9c08c181a0a b8d58c5a2aa5 07bd2624d707 d483b3caefc9 a5d0db83bf1a de55d0bbf509 3426452d9c80 7e526115c56e bc3605e12eff d2f72cae6a64 62053b229810 3ca4208a02b3 a4fc98bde05d	Approved
0	201f6f4c9f30	201f6f4c9f30	Approved

Findings

Nothing raised yet.

---

@hermes-exosphere help lists every command. This comment is maintained in place — I rewrite it after each review rather than posting a new one.

[hermes-exosphere]

Hermes found no blocking issues in this revision.

[hermes-exosphere]

Hermes found no blocking issues in this revision.

[hermes-exosphere]

Hermes found no blocking issues in this revision.