Plane at three fields and three answers: 12,510 titles, 358 fingerprints and 72 product matches

When three fields return three different numbers for one product, the instinct is to look for the correct one. For Plane, a project management platform, the more useful response is to establish what question each field answers and to stop treating them as competing estimates of one quantity.

Context and method

Queries ran through the ZoomEye SDK on 2026-10-05 with sub_type=all, page=1 and pagesize=1. Page size limits returned records, not matched totals.

• Search: title="Plane" returned 12,510.
• Comparison: app="Plane" returned 358.
• Comparison: product="Plane" returned 72. All three figures describe globally indexed assets at collection time. None indicates that a workspace is reachable, unauthenticated or vulnerable.

What separates the numbers

The title figure is the most permissive of the three, and for a short and common word it is also the least precise. A product name that can appear as an ordinary noun will accumulate matches from pages where the word is used for other reasons, which is a specific hazard here that was not a factor for the longer product names measured elsewhere in this series.
The application field is stricter, since it depends on recognisable behaviour rather than on a string. Its value is the most plausible population indicator of the three, subject to the usual caveat that client-rendered interfaces reduce coverage.
The product field reflects a component-level representation that covers some application classes and not others. As with other products measured in this series, a value one or two orders of magnitude below the fingerprint count is a coverage statement rather than a deployment statement.

Why the platform is worth reviewing

A project management platform holds the organisation's plans, issue descriptions, attachments and, in many deployments, the integrations that connect it to source control, chat and automation. The integration credentials are the sensitive part: a task tracker that can post to a chat channel, merge a pull request or trigger a deployment is a system with standing authority, and its own authentication is the only barrier in front of that authority.
Public projects add a second dimension. Where a workspace has published projects for external visibility, the same application serves both an intentionally public surface and a private one, and the distinction depends on configuration that an external observer cannot verify.

Reporting method

Report each field with its query and collection time, and describe what it measures rather than ranking the three into one figure. Where a product name is a common word, state that the title field over-collects and prefer the fingerprint field for population questions. Where the fingerprint field returns a very small number for a widely deployed product, state that the field does not cover the application class.

Limitations

This is a single collection, and the three figures are not directly comparable to counts gathered under a different sub_type. No claim is made about the security posture of any deployment. The title field in particular should not be used for trend analysis for a name of this kind.

References

• ZoomEye, title="Plane" (12,510), app="Plane" (358) and product="Plane" (72), sub_type=all, collected 2026-10-05.
• Plane project documentation, workspace and integration configuration.