Ecosystem · Swift · CocoaPods, SwiftPM
Vulnerabilities in your iOS dependencies, Swift Package Manager and CocoaPods.
LibWatch reads Package.resolved and Podfile.lock, checks every dependency and tracks the Swift version and the minimum iOS version.
What LibWatch reads in the repository
Package.swiftPackage.resolvedPodfilePodfile.lock
Language version: Swift and minimum iOS version
Nothing else: no cloning, no code run.
What LibWatch checks
The dependencies, and the iOS target
Swift and CocoaPods packages
Known vulnerabilities
Every Swift package checked against OSV; a pod, through the Git repository of its podspec, with a result to confirm.
Swift version
End of life
The declared version is tracked: you know when it stops getting fixes.
Health
License policy
Licenses that conflict with your project's policy are flagged.
An alert, in practice
A vulnerability in a Swift package, with the version that fixes it
The vulnerabilities that affect your versions, with the fixed version. Nothing more.
Real severity
CVSS severity and presence in the CISA KEV catalog
What to do
The fixed version, and the affected project
Where
Email, Slack, Zulip or webhook, set per project
customer-app · iOS
Example · analysis from October 22
-
Outdated target
Minimum iOS
iOS 14
-
Low severity
Alamofire
5.6.1
-
Up to date
Kingfisher
8.1.0
Rechecked every night at 2 a.m.
Tracked versions
Swift version and minimum iOS target, read from the Xcode project and Package.swift.
- Package.swift · swift-tools-version
- Xcode project · IPHONEOS_DEPLOYMENT_TARGET
- Podfile · platform :ios
Get started
Your first report in a few minutes
No pipeline to change.
Connect GitHub or GitLab
Self-hosted GitLab instances included.
Choose your iOS repositories
LibWatch finds the files listed above on its own, even in a monorepo.
Read the report, set up alerts
Exploited vulnerabilities first, fixed versions, language end of life.
Frequently asked questions
LibWatch and iOS
Do I need to install anything in the project?
No. LibWatch reads dependency files through the GitHub or GitLab API, without adding anything to your pipeline.
Are private registries supported?
Yes. A package from a private registry is identified as such: its name is never sent to a third-party service, and it stays in the project's inventory.
Does LibWatch detect the version installed on the server?
No. LibWatch reads the version declared in the repository (version file, lockfile or manifest). It has no access to your servers.