LibChecker

Android app inspection, community-maintained library rules, and APK analysis on the web.
查看应用使用的库，比较更新前后的差异。

Download · WebUI · Documentation · Contribute rules · Community

LibChecker for Android inspects installed apps and package files, identifies libraries and SDKs, and compares app snapshots. WebUI and the Telegram bot bring package analysis to the browser and chat. They share the community's library identification data through LibChecker-Rules and LibChecker-Rules-Bundle.

Solid arrows show data, build inputs, or published artifacts moving to a consumer. Dashed arrows show editing or documentation relationships. The diagram includes private tools; their links require repository access.

flowchart TB
  subgraph authoring["Rule authoring and import tools"]
    generator["LibChecker-Rules-Generator<br/>Private desktop rule editor"]
    importer["lc-add-rules<br/>Rule JSON to SQLite Action"]
  end

  subgraph data["Rules and distribution"]
    rules["LibChecker-Rules<br/>Identification rules and remote metadata"]
    bundle["LibChecker-Rules-Bundle<br/>Android SDK, rule database and icons"]
    assets["assets<br/>CI APKs, update metadata and size history"]
  end

  subgraph products["Applications"]
    android["LibChecker<br/>Android app"]
    web["tgbot<br/>Telegram bot, WebUI and shared analyzer"]
    windows["LibChecker-for-Windows<br/>Private Windows prototype"]
  end

  subgraph community["Documentation and discovery"]
    docs["LibChecker-Docs<br/>User guides"]
    profile[".github<br/>Organization profile"]
  end

  generator -.->|"Edit local rule files"| rules
  rules -->|"Rule JSON input"| importer
  bundle -->|"Icon resource mapping"| importer
  rules -->|"Online rules and metadata"| android
  bundle -->|"Bundled rules and Android API"| android
  rules -->|"Rule detail generation"| web
  bundle -->|"Database and icon generation"| web
  android -->|"Feature icon source"| web
  android -->|"CI APKs and version metadata"| assets
  assets -->|"Update metadata"| android
  docs -.->|"Usage guides"| android
  profile -.->|"Project navigation"| android
  profile -.->|"Documentation entry"| docs

• Rules have two delivery paths. The Android app uses the bundled SDK and also reads online rule data. The bot/WebUI build generates local JavaScript data from the bundle's database and icons, enriched with metadata from the rules repository. App information exported from Android can also be opened in WebUI.
• Import tooling is separate from publication. lc-add-rules can insert rule JSON into a supplied SQLite database using the bundle's icon mapping. Its presence does not imply an active automatic Rules → Bundle release pipeline.
• Windows is a prototype. It is shown for completeness; no shared-rule integration is represented for it.

• Improve identification: submit a missing or incorrect library rule, or read the chart rule contribution guide.
• Improve the apps: report Android issues in LibChecker and bot/WebUI issues in tgbot.
• Help more people use LibChecker: contribute translations or improve the documentation.
• Talk with the community: join GitHub Discussions or Telegram.