What each HTML column means
| Field | Meaning | How to read it |
|---|---|---|
| Type | The object being counted, such as Property, Method, FileName or a localization key. | First identify whether the row is code, a file, a configuration key or a text signal. |
| Project A / B total | The count of objects found in each project. | Use both totals to understand whether the two projects have a similar scale. |
| Same count | The number of objects identified as matching. | A larger count means a larger reviewable intersection in that dimension. |
| Matching-item list | Names or representative samples found in both projects. | This is the most direct evidence and can lead you back to the full local report. |
| Similarity | The percentage calculated for that dimension. | Read it with totals and matching names; one dimension is not the whole conclusion. |
How to read the real example
The sanitized report shown on this website compares FactorizationWanIndexes and HUMBbbMonitoring. In the example:
- Properties: 782 in A, 355 in B, 18 matching, 2.3% similarity.
- Localization keys: 1,488 on each side, 353 matching, 23.72% similarity.
- Folder names: 26 in A, 28 in B, 14 matching, 50% similarity.
- File hashes: 223 / 599 files were inventoried, with no matching content hashes in this example.
These numbers demonstrate the report structure and reading method. Actual results depend on project content, configuration and exclusions.
Similarity and display-only rows
The example uses the equal_mean method for overall similarity and a minimum comparison string length of 2. Code and resource dimensions keep their own summaries; the overall value does not replace checking the matching items.
Some categories are displayed for inventory but excluded from similarity calculation. Objective-C enum rows, for example, can be marked as display-only; empty or unavailable dimensions may show a dash.
Three output formats
| Format | Best for | What you see |
|---|---|---|
| HTML | Human review | Readable category tables, matching names, summaries and path relationships. |
| JSON | Programmatic use | Structured overall, code and resource comparison data. |
| LOG | Run diagnosis | When scanning, comparison and file writing happened. |
The homepage's “What exactly is compared?” area switches among these views and among code, strings, resources and matching details.