LibChecker-Rules

English | 简体中文

This repository maintains the rules and metadata used by LibChecker. It covers Android component and native library identification, Flutter engine version mappings, and declarative statistics for the chart page.

Repository contents

Path	Contents
native-libs/, activities-libs/, services-libs/, receivers-libs/, providers-libs/, actions-libs/, static-libs/	Identify libraries and SDKs from native libraries, Android components, and intent actions.
flutter_hash/	Maps engine revisions found in libflutter.so to possible Flutter releases.
chart/	Contains chart rules, SVG icons, JSON Schemas, tests, and generated bundles.
configuration/, cloud/	Contains versioned configuration and rule data consumed by LibChecker.

Contributing

Library identification rules

If a library identification rule is missing or incorrect, open the issue chooser and select Submit new rule or Bug report. Follow the template and provide the filename, library name, development team, description, and a primary source. Include the app name and version when a sample is available for verification. Icons must use the SVG format.

Chart rules

Chart rules have their own schema, tests, and release process. New rules normally start in the preview channel and move to the stable channel after verification. Read the complete contribution guide before submitting a rule:

• English contribution guide
• 简体中文贡献指南

If your AI agent supports Skills, install the chart rule Skill from this repository:

npx skills add LibChecker/LibChecker-Rules

See the chart rule Skill guide for installation and usage details.

License

This repository is licensed under the Apache License 2.0.

Canonical base rules (v5)

Edit libraries/<UUID>.json and icons/; legacy per-name JSON and DB are compatibility outputs. The v5 contract documents editor fields, matching, SVG validation, manifests, migration audit and staged rollout.

python3 tools/rules.py check
python3 -m unittest discover -s tests -v
python3 tools/rules.py build --output /tmp/libchecker-rules

Python compilation uses only the standard library; cross-language tests also need Node.js and a JDK. import-icon validates an SVG and automatically appends its icon index. Generated artifacts share one source revision and dataVersion; normal source changes publish through the serialized own-repository workflow after merge to v4. SDK details and chart pipelines remain independent.