Configuration and inputs
Choose the input contract for the command you are using. A SwiftPM package, a source-text directory, and an admitted immutable manifest are different inputs.
| Workflow | Required input | Preparation |
|---|---|---|
| source-scan | Package.swift directory, product name, explicit build authorization | Managed discovery and indexed build in the qualified profile |
| experimental-scan | Swift source file or directory | Local parsing; no build or index |
| doctor, stats, scan, why | Owner-supplied admitted immutable manifest bundle | Preserve the bundle's bound files, facts and build identity |
Source-scan configuration#
--package-path and --product select the product. --allow-build is required before package evaluation and compilation. --include-stdio-rules is false by default. --format defaults to human and can be json.
There is no source-scan YAML configuration, arbitrary rule switch, Index Store path switch or source export option in the documented command. Do not borrow flags from the manifest or preview workflows. CLI reference is extracted from this exact executable.
Immutable manifests#
Manifest validation checks the bound snapshot, capabilities, profiles, completeness and integrity of its admitted facts. A path alone is not evidence. Use the existing-snapshot guide when an owner has supplied a qualified bundle. Do not manually mark an open world as complete.
Build effects and data#
Analysis is local. Authorized builds may evaluate package code and use the network for locked dependencies. Source-scan removes its owned temporary acquisition directory after the request. Reports can contain source identifiers and paths; handle them as project artifacts when sharing or retaining them.