Work with an existing snapshot
Use manifest commands only when the owner has supplied an admitted immutable snapshot bundle and its analysis manifest. An arbitrary Xcode Index Store is not a ready analysis snapshot.
Required input#
The supplied manifest binds the selected build configuration, compiler facts, inputs, completeness and provenance. Keep the bundle's files together at the locations expected by the manifest. Ask its supplier for the exact profile, allowed rule selection and scope of the snapshot.
This CLI does not expose a general command that turns any existing Index Store into a qualified manifest. Do not fabricate one from a folder path or edit quality flags to make validation pass. For a small supported SwiftPM product, use source-scan instead.
Validate, then inspect#
Replace /path/to/manifest.json with the manifest supplied with your bundle:
"$ANALYZER" doctor --manifest /path/to/manifest.json --format json
"$ANALYZER" stats --manifest /path/to/manifest.json --format json
"$ANALYZER" scan --manifest /path/to/manifest.json --format jsonDoctor validates trust and admission; stats describes admitted facts. A successful doctor result does not prove that every desired rule or negative conclusion is available. Read quality, capabilities, reasons and the declared build world.
Ask why a subject is reachable#
why requires an exact canonical declaration identity or strongly connected component (SCC) identity from the supplied snapshot. An SCC is a group of graph nodes that can each reach every other node in that group. The command is not a free-text symbol search. Choose shipping or repository scope and the relevant code, API, ABI or runtime dimension. See CLI reference for the options.
Keep this workflow separate#
Manifest analysis and source-scan have different input and output contracts. The source-scan tutorial's counts and results do not qualify your manifest bundle. Availability depends on its admitted facts and the requested analysis. Do not add --gate by default; CI guidance remains advisory.