Dependency tree
What one Forge scan resolved from npm metadata on 2026-08-28 — observed resolution, not a publisher declaration.
60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.
ajv8.20.04 dependencies
- fast-deep-equal3.1.3
- fast-uri3.1.6
- json-schema-traverse1.0.0
- require-from-string2.0.2
- mailkite0.19.0
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.0shown above
- zod4.5.1
cors2.8.6+1 not drawn1 dependency
- hono4.13.5
- jose6.2.10
express5.2.1+27 not drawn1 dependency
- raw-body3.0.2+4 not drawn
ajv-formats3.0.11 dependency
- cross-spawn7.0.6+3 not drawn
eventsource3.0.71 dependency
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.6.2+2 not drawn
- zod-to-json-schema3.25.2
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
Declared but not resolved
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
- package cap reached: 49
- below the depth cap: 5
- wrappy 1 — required by once@1.4.0package cap reached
- http-errors ^2.0.1 — required by send@1.2.1package cap reached
- mime-types ^3.0.2 — required by send@1.2.1package cap reached
- ms ^2.1.3 — required by send@1.2.1package cap reached
- on-finished ^2.4.1 — required by send@1.2.1package cap reached
- range-parser ^1.2.1 — required by send@1.2.1package cap reached
- statuses ^2.0.2 — required by send@1.2.1package cap reached
- ms ^2.1.3 — required by debug@4.4.3package cap reached
- debug ^4.4.0 — required by router@2.2.0package cap reached
- depd ^2.0.0 — required by router@2.2.0package cap reached
- is-promise ^4.0.0 — required by router@2.2.0package cap reached
- parseurl ^1.3.3 — required by router@2.2.0package cap reached
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.
