Skip to content

Detection: two-step resolution seam (isOutbound -> resolveProvider), emit unknown outbound instead of dropping, enrich capture #146

Description

@AndresL230

Part of #142.

Summary

Today a call that's clearly outbound but unattributed is silently discarded at two points: detection (src/scanner/core-scanner.ts:269if (!fp && !knownSdkProvider && !knownHttpHost) continue;) and endpoint aggregation (src/scan-results.ts isHighConfidenceEndpointUrl rejecting sdk:// placeholders — see #141). This makes "unknown provider" and "not a call" indistinguishable. Per the agreed design, an outbound-but-unknown call should become a logged known-unknown with a captured "calling card" so providers can be backfilled.

Proposed fix

Acceptance criteria

Related: #141, #136.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/detectiondocs/accuracy/detection.md — finding every call site, attributing correctlyenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions