TNT-Likely/BeeCount

Local-first bookkeeping for iOS/Android/Web · Self-hosted cloud + iCloud/WebDAV/S3 sync · AI capture · MCP | 本地优先的跨端记账 · 自建云 + iCloud/WebDAV/S3 同步 · AI 记账 · MCP

What is TNT-Likely/BeeCount?

TNT-Likely/BeeCount is a repository whose own project materials describe it as Local-first bookkeeping for iOS/Android/Web Self-hosted cloud + iCloud/WebDAV/S3 sync AI capture MCP + iCloud/WebDAV/S3 AI MCP - AI , , GLM-4 - OCR TFLite + GLM , / / - ,GLM 50 - Android / iOS. This Graphify demo keeps TNT-Likely/BeeCount as the primary keyword while adding source-derived context, README signals, and an interactive code graph for deeper exploration.

Source: README.md at ea038fb7fd67

Graphify architecture insights for TNT-Likely/BeeCount

TNT-Likely/BeeCount has a large Graphify map with 15,935 nodes, 20,663 edges, and 312 communities. The graph turns TNT-Likely/BeeCount into an architecture map: dense communities point to related implementation areas, while high-degree nodes from the Graphify report are good starting points for code review, onboarding, and dependency exploration.

README-derived project notes

  • TNT-Likely/BeeCount is described by its project source as: Local-first bookkeeping for iOS/Android/Web Self-hosted cloud + iCloud/WebDAV/S3 sync AI capture MCP + iCloud/WebDAV/S3 AI MCP - AI , , GLM-4 - OCR TFLite + GLM , / / - ,GLM 50 - Android / iOS
  • The project README exposes reader-facing sections such as BeeCount Cloud, Web, and Star History, which helps explain how TNT-Likely/BeeCount is positioned and used
  • TNT-Likely/BeeCount was captured from the repository at commit ea038fb7fd67 and analyzed in code-only mode, so this page connects project documentation with the generated code graph
  • TNT-Likely/BeeCount is primarily a Dart project, which makes the graph useful for understanding important files, modules, and dependency relationships before opening the source tree

Related code graphs

Graphify report highlights

Summary

  • 15935 nodes · 20663 edges · 312 communities (293 shown, 19 thin omitted)
  • Extraction: 100% EXTRACTED · 0% INFERRED · 0% AMBIGUOUS · INFERRED: 26 edges (avg confidence: 0.8)
  • Token cost: 0 input · 0 output

God nodes

  • primaryColorProvider - 190 edges
  • repositoryProvider - 149 edges
  • currentLedgerIdProvider - 95 edges
  • BeeDatabase - 49 edges
  • statsRefreshProvider - 35 edges
  • currentLedgerProvider - 28 edges

Surprising connections

  • _showOverlay --references--> primaryColorProvider [EXTRACTED]
  • _loadInitial --references--> repositoryProvider [EXTRACTED]
  • loadMore --references--> repositoryProvider [EXTRACTED]
  • refresh --references--> repositoryProvider [EXTRACTED]

FAQ about TNT-Likely/BeeCount

What is TNT-Likely/BeeCount?

TNT-Likely/BeeCount is described by its repository as Local-first bookkeeping for iOS/Android/Web Self-hosted cloud + iCloud/WebDAV/S3 sync AI capture MCP + iCloud/WebDAV/S3 AI MCP - AI , , GLM-4 - OCR TFLite + GLM , / / - ,GLM 50 - Android / iOS. This page adds a Graphify code graph so readers can inspect how the project is structured.

What does the TNT-Likely/BeeCount Graphify graph show?

TNT-Likely/BeeCount has a large Graphify map with 15,935 nodes, 20,663 edges, and 312 communities. It highlights communities, important nodes, and relationships extracted from the captured source commit.

Why use Graphify to explore TNT-Likely/BeeCount?

Graphify gives TNT-Likely/BeeCount a visual architecture layer, making it easier to find central files, understand module boundaries, and decide where to start reading the code.

Where did the TNT-Likely/BeeCount page content come from?

The project notes are derived from README.md at ea038fb7fd67, repository metadata, and the Graphify report generated for the captured commit.

Editorial review · repository graph

What this page is based on

The graph is an observed repository artifact; the selected snapshot date defines what was inspected.

Review basis
repository graph record and linked primary evidence
Last checked
Jul 9, 2026
Evidence links
3 recorded in the page data

Source snapshot is 92 days old; verify upstream details before relying on pricing, availability, or security claims.