Supported environments
The first-analysis results are reproduced with Apple Swift 6.3.3, arm64, macOS 26, using profile apple-swift-6.3.3-macos-arm64 and product revision 524fa07e. This is the documented native profile, not a cross-platform qualification claim.
Source-scan envelope#
| Input property | Documented boundary |
|---|---|
| Package type | Selected SwiftPM library or executable product |
| Source census | At most 16 source files, subject to combined authored/generated limits |
| Module census | At most 16 modules |
| Source size | At most 262,144 bytes per source and 2,097,152 bytes in total |
| Dependency input | Filesystem or locked Git closure within the bounded envelope |
| Native input | Acquisition may capture it; native semantic effects remain unknown |
| Resources and generated code | Only admitted forms; unsupported processing remains unavailable |
| Policy selection | No application policy required for the selected nine or eleven conditions |
These are upper bounds, not a promise that every smaller package is supported. Other acquisition and evidence requirements still apply.
Not established by this qualification#
Arbitrary Xcode projects, full iOS applications, Linux/Windows execution, every Swift compiler/SDK combination, opaque native behavior and a full self-scan of the analyzer are not qualified by the tutorial. Additional registered rules or internal tests do not expand that claim.
An iOS developer can evaluate the small SwiftPM workflow on the documented Mac profile. This does not mean the CLI scans every iOS build configuration. Troubleshooting explains how to read refusal reasons.
Evaluating code from an iOS project#
Start with a small SwiftPM product that builds for the documented macOS host, such as platform-independent application logic. Moving an iOS target into Package.swift does not make its UIKit-dependent code a supported macOS input. If the selected code requires an iOS SDK, this tutorial does not establish that it can be built or analyzed; inspect the build or acquisition refusal instead of interpreting it as zero issues.
The captured source-scan command has no documented iOS SDK, simulator or Xcode destination selector. Do not add a guessed destination flag. Build conditions such as canImport(UIKit) can exclude iOS-only code in a macOS build: results for that admitted variant do not cover the excluded code. See the exact command help and coverage model.