Check your own app — free, in about a minute.
The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.
Run the free mini-scan →Short answer: Package.resolved is the most honest file in your iOS project — it records the exact version and commit of every Swift package your app ships, including the transitive ones you never chose. Auditing it means reading that list, checking the pinned versions against known-vulnerability data, and treating branch-based pins as what they are: un-auditable moving targets. It takes fifteen minutes and it's the only dependency review that reflects what actually goes into your binary.
Every time SPM resolves your dependencies, it writes Package.resolved — in an app project, at YourApp.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved; in a Swift package, at the repo root. Each entry carries:
That last field is the point. Package.swift records what you asked for (a version range, a branch, a minimum). Package.resolved records what you got. Security review against the manifest is auditing your intentions; review against the resolved file is auditing your app.
Two habits follow from that:
Package.resolved to git. For apps, the resolved file is what makes builds reproducible — and what makes a review like this one possible at all. If it isn't in the repo, every build (and every reviewer) resolves a potentially different graph.1. Take inventory. Open the file and list every package, direct and transitive. For each one, you should be able to answer: do I know what this is, and which of my dependencies pulled it in? Entries you can't explain deserve a search before anything else on this list.
2. Check the pinned versions against vulnerability data. Known-vulnerability checking needs an exact version to look up. OSV covers GitHub-hosted Swift packages (the SwiftURL ecosystem, fed by GitHub's advisory database): give it the repository and the resolved version and it reports published advisories. A pinned version with a known CVE ships that CVE in your app until you bump it. PreShipIt's project upload scan runs exactly this lookup for the exact pins in your Package.resolved (and exact: requirements in Package.swift) — or run it by hand, package by package, on osv.dev.
3. Flag the pins that can't be checked. This is where honesty matters:
branch: "main") resolve to whatever the branch head is on build day. There's no fixed version to audit, and next month's build may silently contain different code. Fine for development spikes; a liability in a shipped app. Convert them to version pins.from: "1.0.0") are only as safe as the resolved version they produced — check the resolved entry, not the range.4. Check the upstreams, not just the versions. For each package: is the repo archived? When was the last release, and does the maintainer respond to security issues? A package can have no known CVEs and still be a dead end — the next vulnerability found in it will simply never be fixed.
5. Update deliberately, then re-resolve. swift package update (or Xcode's "Update to Latest Package Versions") moves the resolved pins. Do it on a schedule rather than in a panic, run your tests, and diff Package.resolved before and after — that diff is your record of what changed in the code you ship.
If your project uses CocoaPods, the equivalent inventory is Podfile.lock — same discipline applies (read it, know every entry, keep it committed). One honest tooling gap: OSV has no CocoaPods ecosystem feed, so automated CVE checking for pods mostly doesn't exist; our upload scan inventories the pods and says so in the report rather than pretending to have checked them. Manual advisory-checking for big pods is the current state of the art.
Package.resolved is committed and currentYour users can't see your dependency graph, but they run it. Fifteen minutes with this one file is how you find out whether you're shipping someone else's known vulnerability as your own.
Related: 7 Vibe Coding Security Mistakes — stale and unexamined dependencies are one of the recurring seven, right alongside the secrets and debug flags.
The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.
New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.
Check your own app — free, in about a minute.
The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.
Run the free mini-scan →← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report