Excessive API visibility

Rule ID: api.access-narrowing@1.0.0. Availability below refers to source-scan at product 524fa07e.

V-ARCH-04 — Excessive API visibility#

Excessive API visibility. It examines repository-wide reachability, dependencies, resources, and API boundaries.

Availability#

Not available in source-scan. There is no source-scan flag to activate this condition.

Example and action#

Illustrative pattern only. This is not a complete runnable package or a reproduced source-scan result. Helper APIs and omitted context must be supplied by the application.

swift

public struct InternalCache { }

Inspect the consumers, runtime registrations and selected build variants before removing or narrowing an API. Preserve externally observable behavior.

swift

internal struct InternalCache { }

Intended analysis#

Intended reasoning: Model declarations, uses and entry points as a graph. A dependency or visibility decision needs the relevant consumers and build variants; an absence claim additionally needs a closed, complete graph. Required evidence: reachability, dependency, resource, and API-boundary facts

Assumptions and unknown#

The relevant facts must be admitted for the selected immutable build world. Unknown aliases, external effects, unsupported source forms or incomplete consumers can prevent a conclusion. Availability in this workflow is stated above; the illustration does not expand that availability.

Evidence and interpretation#

The target catalog describes the intended condition. It is not evidence of an active source-scan diagnostic.

Historical evidence at 4558458d: accepted-subset (a limited set of source forms and profiles passed historical checks). That evidence has not been requalified for this product revision.

How we validate checks explains the evidence boundary. Foundations separates method assumptions from implementation claims.