An OpenPGP implementation for iOS and macOS providing encryption, decryption, signing, and verification.
ObjectivePGP is an open-source library for iOS and macOS that implements the OpenPGP protocol. It provides tools for encryption, decryption, digital signing, and signature verification, allowing developers to secure data and communications in their applications. It addresses the need for robust, standards-based cryptographic functionality on Apple platforms.
iOS and macOS developers building applications that require email encryption, secure messaging, data integrity verification, or any OpenPGP-compliant cryptographic operations.
Developers choose ObjectivePGP because it offers a complete, security-audited implementation of OpenPGP specifically for Apple ecosystems, supports both Objective-C and Swift, and is available under a flexible dual license for commercial and non-commercial use.
ObjectivePGP is an open-source library for iOS and macOS that provides developers with tools for implementing OpenPGP encryption and decryption, digital signing, and signature verification in their applications, thereby enhancing security and data integrity.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides a full suite of OpenPGP features including encryption, decryption, signing, verification, and key management, as detailed in the key features and usage examples.
Has undergone a complete security audit by Cure53, adding credibility for production use, as mentioned in the README's security section.
Offers free use for non-commercial projects and a commercial license for paid apps, catering to diverse business needs as explained in the license section.
Specifically built for iOS and macOS with support for Swift Package Manager, CocoaPods, and pre-built frameworks, ensuring seamless setup per the installation guide.
Only supports iOS and macOS, limiting its utility for cross-platform or server-side applications that require PGP operations on other systems.
The README explicitly states 'Known limitations: Cleartext signature,' which may hinder certain email or document verification use cases.
Requires contacting the author for commercial license details, creating uncertainty compared to libraries with transparent pricing or open-source terms.