IPFS-portal/graphify-out/GRAPH_REPORT.md

Graph Report - . (2026-06-27)

Corpus Check

• Corpus is ~21,600 words - fits in a single context window. You may not need a graph.

Summary

• 251 nodes · 401 edges · 17 communities (12 shown, 5 thin omitted)
• Extraction: 100% EXTRACTED · 0% INFERRED · 0% AMBIGUOUS · INFERRED: 2 edges (avg confidence: 0.8)
• Token cost: 0 input · 0 output

Community Hubs (Navigation)

• _COMMUNITY_Portal Layout & Navigation
• _COMMUNITY_Landing & Payment UI
• _COMMUNITY_Payment Smart Contract
• _COMMUNITY_IPFS Gateway & History
• _COMMUNITY_Explorer Components
• _COMMUNITY_NPM Dependencies
• _COMMUNITY_TypeScript Config
• _COMMUNITY_API Routes & Proxy
• _COMMUNITY_File Preview
• _COMMUNITY_Static Server
• _COMMUNITY_Root Layout
• _COMMUNITY_Sidebar Navigation
• _COMMUNITY_Deploy Script
• _COMMUNITY_Next.js Config

God Nodes (most connected - your core abstractions)

1. PaymentService - 31 edges
2. compilerOptions - 16 edges
3. WalletProvider - 15 edges
4. apiFetch() - 12 edges
5. getInjectedProvider() - 7 edges
6. GET() - 6 edges
7. formatWeiToETH() - 6 edges
8. proxyIPFS() - 5 edges
9. POST() - 5 edges
10. DELETE() - 5 edges

Surprising Connections (you probably didn't know these)

• AdminPaymentPage() --calls--> formatWeiToETH() [EXTRACTED] src/app/admin/payment/page.tsx → src/lib/wallet.ts
• UploadPage() --calls--> GatewayLink() [INFERRED] src/app/upload/page.tsx → src/app/explorer/components/GatewayLink.tsx
• PaymentPanel() --calls--> formatWeiToETH() [EXTRACTED] src/components/PaymentPanel.tsx → src/lib/wallet.ts
• DirectoryListingProps --references--> IPFSEntry [EXTRACTED] src/app/explorer/components/DirectoryListing.tsx → src/lib/api.ts

Import Cycles

• None detected.

Communities (17 total, 5 thin omitted)

Community 0 - "Portal Layout & Navigation"

Cohesion: 0.08 Nodes (28): PinBadgeProps, PeerData, PinData, Status, addPin(), apiFetch(), BWStats, checkHealth() (+20 more)

Community 1 - "Landing & Payment UI"

Cohesion: 0.08 Nodes (30): PaymentPanel(), PaymentPanelProps, TOKEN_ICONS, listUsers(), ERC20_ABI, IPFS_PORTAL_PAYMENT_ABI, MAOSDiscountTier, PriceInfo (+22 more)

Community 3 - "IPFS Gateway & History"

Cohesion: 0.11 Nodes (21): GatewayLink(), GatewayLinkProps, formatBytes(), HistoryPage(), uploadFile(), addToHistory(), clearHistory(), DEFAULT_SETTINGS (+13 more)

Community 4 - "Explorer Components"

Cohesion: 0.09 Nodes (13): BreadcrumbSegment, BreadcrumbsProps, CIDInputProps, DirectoryListingProps, FileIconProps, BreadcrumbSegment, ExplorerPage(), ExplorerState (+5 more)

Community 5 - "NPM Dependencies"

Cohesion: 0.08 Nodes (24): dependencies, clsx, lucide-react, next, postcss, react, react-dom, @tailwindcss/postcss (+16 more)

Community 6 - "TypeScript Config"

Cohesion: 0.10 Nodes (19): compilerOptions, allowJs, esModuleInterop, incremental, isolatedModules, jsx, lib, module (+11 more)

Community 7 - "API Routes & Proxy"

Cohesion: 0.44 Nodes (10): DELETE(), GET(), handleHealth(), mapToKuboAPI(), matchRoute(), POST(), proxyIPFS(), proxyResult() (+2 more)

Community 8 - "File Preview"

Cohesion: 0.38 Nodes (4): detectFileType(), FilePreview(), FilePreviewProps, renderMarkdown()

Community 9 - "Static Server"

Cohesion: 0.33 Nodes (5): fs, http, MIME, path, ROOT

Knowledge Gaps

• 79 isolated node(s): deploy.sh script, nextConfig, name, version, private (+74 more) These have ≤1 connection - possible missing edges or undocumented components.
• 5 thin communities (<3 nodes) omitted from report — run graphify query to explore isolated nodes.

Suggested Questions

Questions this graph is uniquely positioned to answer:

• Why does PaymentService connect Payment Smart Contract to Landing & Payment UI? High betweenness centrality (0.153) - this node is a cross-community bridge.
• Why does http connect Static Server to Payment Smart Contract? High betweenness centrality (0.029) - this node is a cross-community bridge.
• Why does WalletProvider connect Payment Smart Contract to Landing & Payment UI? High betweenness centrality (0.017) - this node is a cross-community bridge.
• What connects deploy.sh script, nextConfig, name to the rest of the system? 79 weakly-connected nodes found - possible documentation gaps or missing edges.
• Should Portal Layout & Navigation be split into smaller, more focused modules? Cohesion score 0.08194905869324474 - nodes in this community are weakly interconnected.
• Should Landing & Payment UI be split into smaller, more focused modules? Cohesion score 0.08305647840531562 - nodes in this community are weakly interconnected.
• Should IPFS Gateway & History be split into smaller, more focused modules? Cohesion score 0.1111111111111111 - nodes in this community are weakly interconnected.