RVS_UIKit_Toolbox
keychain-swift
Our great sponsors
| RVS_UIKit_Toolbox | keychain-swift | |
|---|---|---|
| 1 | 2 | |
| 2 | 2,711 | |
| - | - | |
| 6.0 | 5.2 | |
| 18 days ago | 15 days ago | |
| Swift | Swift | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
RVS_UIKit_Toolbox
-
Log4j: The Pain Just Keeps Going and Going
> I don't think I could in good conscience recommend your approach as a general practice.
I can live with that, but ... (There's always a "but")
I am not happy at all, with the general industry practice of writing every project to be something that can be understood by inexperienced, undisciplined coders.
Every language and programming methodology has an "advanced" type of thing, requiring people to have experience and/or book-larnin'.
I write Swift at a fairly advanced level. I am not at the level of some heavy-duty advanced Swift people, but I am pretty "idiomatic," in my approach. It is not "rewritten TypeScript," like so much code out there.
My code is very well-documented, and I hold myself to standards of Quality that most folks in the industry consider to be obsessive to the point of insanity. My testing code usually dwarfs my implementation code, and my documentation is, let's say ... complete. You can see what I mean in my latest module[0].
I won't write junk, so that someone used to junk, can comprehend it. If people aren't willing to learn enough to understand my middle-of-the-road semi-advanced Swift, then I can't help them. Swift is an awesome language. I feel that we are doing ourselves a disservice, if we do not explore it.
I write for myself. I write code and documentation that I want to use (and I use it). I really don't care, whether or not someone else "approves" of it. I am not relying on others to review, maintain, or patch my code.
When I do use other people's code, I vet it fairly carefully. Including a dependency is a really serious matter. I'm handing full control of my execution context to code that someone else wrote. I'd damn well better take that Responsibility seriously.
[0] https://github.com/RiftValleySoftware/RVS_UIKit_Toolbox
keychain-swift
-
WidgetKit + REST authentication
You should be using Keychain for all secrets. You can specify an "access group" that can be used across processes. The API sucks so I use the keychain-swift wrapper.
-
Log4j: The Pain Just Keeps Going and Going
The only one of those that I didn't write, was KeychainSwift[0]. It makes dealing with the Keychain easy, and is a very simple dependency. If it went off the rails, I'd write something like it, myself.
All the others, are in my own repos, as top-shelf-quality open-source modules.
[0] https://github.com/evgenyneu/keychain-swift
What are some alternatives?
log4shell-tools - Tool that runs a test to check whether one of your applications is affected by the recent vulnerabilities in log4j: CVE-2021-44228 and CVE-2021-45046
KeychainAccess - Simple Swift wrapper for Keychain that works on iOS, watchOS, tvOS and macOS.
Valet - Valet lets you securely store data in the iOS, tvOS, or macOS Keychain without knowing a thing about how the Keychain works. It’s easy. We promise.
Locksmith - A powerful, protocol-oriented library for working with the keychain in Swift.
SwiftKeychainWrapper - A simple wrapper for the iOS Keychain to allow you to use it in a similar fashion to User Defaults. Written in Swift.
Latch - A simple Swift Keychain Wrapper for iOS, watchOS, and OS X.
KeyClip - KeyClip is yet another Keychain library written in Swift.
SSKeychain
SecurePropertyStorage - Helps you define secure storages for your properties using Swift property wrappers.
SecureEnclaveCrypto - Demonstration library for using the Secure Enclave on iOS
latch - a python bioinformatics framework
GoodPersistence - 💾 GoodPersistence is an iOS library that simplifies caching data in keychain and UserDefaults. Using a property wrapper, it reduces the complexity of implementing caching mechanisms, making it easier for developers to focus on app functionality. Compatible with latest Swift and supports all iOS devices. Easy to install with SPM.