A semantic layer can look like a database endpoint, an API used by a dashboard, or a product management page. Its product fingerprints reflect those interfaces imperfectly. On 2026-10-28 at 22:48 UTC, a bounded ZoomEye SDK probe used the global all scope, page 1, and page size 1. The query app="Cube" returned 87. The query title="Cube.js" returned 1,173.
The application result is the closer product-specific lead. The title result is broader and may include pages that mention the framework without serving a Cube API. A team should preserve both counts and select the app measurement as its primary discovery query, while recording the title comparison as background. Neither number demonstrates that an API accepts anonymous queries.
Cube's security material describes token-based access and a security context used for data-access decisions. External identity systems can supply claims, and the semantic layer can enforce policy before a query reaches the underlying database. The useful follow-up is therefore to identify the API endpoint, the issuer and audience expected by that deployment, and the database identity used for serving.
Ask whether the matched host is a publicly documented demo, an internal analytics service, or a production application. A demo may intentionally expose sample data. A production endpoint needs a reviewed public boundary even if its model contains no sensitive dimensions. Check token validation, tenant context, row or measure restrictions, cache separation, and database grants as one chain.
Do not run ad hoc SQL against an unowned Cube service to see what happens. An owner can test the intended policy with a controlled tenant and a negative case for another tenant. The evidence should show a rejected request before the database returns data, not a generic error that hides where authorization failed.
The query sizes also suggest a useful ownership strategy. A smaller app list can be assigned first. The larger title list can be kept as a research queue for identifying new product fingerprints or public demos. As fingerprints and responses change, the team can narrow the list rather than treating all 1,173 pages as equivalent.
ZoomEye supplies discovery and prioritization. The security decision depends on tokens, claims, data policies, and the database account behind the semantic layer. The app and title numbers help a team choose where to look, not what conclusion to publish.