Platforms

How suitable platform detection works

For software releases, we infer which OS/platforms the package is likely meant for (Windows, Linux, macOS, Android, iOS) from extensions, paths, and the magnet name — without reading file contents.

Pipeline

  1. Load rules from software_platforms.json
  2. Primary: score from file-list category_id + extension (e.g. executable/installable + exe/msi/pima → Windows)
  3. Secondary: path fragments and magnet name tokens (e.g. (x64))
  4. Distro ISO names imply Linux
  5. Write platforms, labels, evidence, and confidence into software_json

Platform signals (summary)

  • Windows — category executable/installable + .exe/.dll/.msi/.pima…
  • Linux — installable + .deb/.rpm/AppImage；发行版 ISO…
  • macOS — .dmg/.pkg / macos 路径
  • Android — .apk/.aab
  • iOS — .ipa
Multi-platform packages can list more than one OS. Empty list means no clear signal — not “unsupported everywhere”. This is not a runtime or install guarantee.

Related

CPU architecture (arch, e.g. amd64) is separate from OS platform. Vertical classification is documented on How resource types are detected.

Software How it works
Report