Komodo is a build and deployment control plane. It can manage resources, run actions, store configuration, and connect to servers and repositories. That makes its permissions more important than a generic application login. A user who can execute an action on a resource may be able to change production even without the Write permission on its configuration.
On November 2, 2026, ZoomEye SDK count-only probes returned 1 match for app="Komodo" and 1,134 for title="Komodo" at sub_type=all, page 1, and page size 1. A refinement query, title="Komodo" && http.body="Komodo", returned 1,076. The body-only query returned 14,571, which is broad enough to include unrelated text and should not be treated as a product fingerprint.
The documentation describes layered permissions and four levels: None, Read, Execute, and Write. A user in multiple groups inherits the union of their permissions. The Everyone mode gives all users the permissions assigned to that group. Resource Syncs can define user groups and permissions at scale. The documentation also states that a resource hidden at None may not appear in the GUI or API results.
The 1,076 combined title-and-body result is a better candidate for product-specific discovery than the 14,571 body-only count, but it still needs verification. A page can mention Komodo without being a Komodo control plane. The small application count shows why one fingerprint can be insufficient for inventory. The result should be reported with its query scope rather than presented as a definitive deployment count.
For a reachable Komodo instance, the review should identify:
Which resource types are connected to production credentials.
Which groups have Execute or Write permission.
Whether an
Everyonegroup is enabled.Whether Resource Syncs grant broad permissions unintentionally.
Which API keys belong to users or service accounts and when they expire.
Whether terminal and build actions are logged and attributable.
Execute permission deserves special attention. It can trigger a deployment without allowing a configuration edit. A responder should test whether a read-only user can invoke a build, restart a service, or access a terminal endpoint. Test the group union with an account that belongs to multiple groups. Confirm that removing a group actually removes the effective permission.
Komodo can make deployment operations consistent. Its risk is concentrated in the permission graph and the credentials attached to managed resources. The ZoomEye result is useful when it leads to that graph, not when it is treated as proof that every match is an exposed control plane.
Query evidence
app="Komodo" returned 1 match, title="Komodo" returned 1,134, and title="Komodo" && http.body="Komodo" returned 1,076. All queries used sub_type=all, page 1, and a page size of 1.