xcode-project-auditor — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited xcode-project-auditor (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use for project- and target-level build inefficiencies. Recommend first and require explicit approval before changing projects, schemes, or build settings.
../../shared/build-optimization/references/build-settings-best-practices.md.xcfilelist, dependency analysis, and timestamp-changing toolsDEFINES_MODULE, and self-contained headersPlanning Swift module, asset catalog compilation, and ExtractAppIntentsMetadata timingPodfile or Pods.xcodeproj exists, recommend SPM migration and avoid CocoaPods-specific optimizationEvery audit includes a build settings checklist for Debug and Release using [x]/[ ]. Scope is build performance only; do not flag language-migration settings such as SWIFT_STRICT_CONCURRENCY or SWIFT_UPCOMING_FEATURE_*.
Apple-aligned checks: accurate target dependencies, schemes in Dependency Order, scripts with declared inputs/outputs, .xcfilelist for many files, consistent explicit module settings, and module-map readiness.
Skip debug-time scripts that only matter in release, add script guards and dependency metadata, remove accidental serial bottlenecks, align settings that create extra module variants, stop formatters/linters from touching unchanged files, split huge asset catalogs into resource bundles, and use Task Backtraces to find the input that triggers invalidation.
For each issue include evidence, scope, whether it affects clean/incremental/both, estimated impact, and approval requirement. If evidence points to package graph or build plugins, read and hand off to swiftpm-build-inspector.
references/project-audit-checks.md../../shared/build-optimization/references/build-settings-best-practices.md../../shared/build-optimization/references/recommendation-format.md../../shared/build-optimization/references/build-optimization-sources.md~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.