3 ms·
> Welcome to how we use open source code. That’s a big reason Software Bills of Materials (SBOM) have become essential for securing the software supply chain.
by ChrisMarshallNY 4y ago
> Welcome to how we use open source code. That’s a big reason Software Bills of Materials (SBOM) have become essential for securing the software supply chain.
I tend to do this, but it's pretty damn easy for me. I have a "2-level-dependency" rule that I generally go by, these days. i.e., Each dependency can have only one dependency, and that dependency can't have any others.
The main way that I deal with it, is to write all my own dependencies, and I don't count toolsets, standard libraries, or platform frameworks (for better, or for ill).
I really, really want dependencies to work. They are a great idea, and I have been promoting modular architecture for decades.
It's just that we are in a "wild west" situation, where we can't trust dependencies.
I'm tired of hearing the phrase "It's a solved problem," with a reference to a dependency.
I don't have the answer. I just have my own rule, which elicits scorn from most modern programmers (I'm painted as a luddite, refusing to "get with the times," or as a "tinfoil-hatter").
WFM. YMMV.
- jeroenhd 4y agoI like the "2-level-dependency" rule, but what do you do when one of your dependencies gains more dependencies? Do you stop updating and start migrating to something else, or maybe maintain a fork of your own? It's a very nice concept, but I kind of have my doubts about maintainability.
- ChrisMarshallNY 4y agoI use my own dependencies. I've written many of them. Some of them, go "deeper," but only in dependencies that I authored. Here's the dependency manifest from the app I'm working on now (From my localization file): // MARK: - // MARK: - DO NOT TRANSLATE BELOW THIS LINE - // MARK: - "SLUG-VERSION-BMLT" = "BMLTiOSLib: 1.4.2"; "SLUG-VERSION-KEYCHAINSWIFT" = "KeychainSwift: 20.0.0"; "SLUG-VERSION-LGVCLEANTIME" = "LGV_Cleantime: 1.3.5"; "SLUG-VERSION-UICLEANTIME" = "LGV_UICleantime: 1.1.1"; "SLUG-VERSION-AUTOFILL" = "RVS_AutofillTextField: 1.3.0"; "SLUG-VERSION-GCD" = "RVS_BasicGCDTimer: 1.5.0"; "SLUG-VERSION-CHECKBOX" = "RVS_Checkbox: 1.2.0"; "SLUG-VERSION-OBSERVER" = "RVS_GeneralObserver: 1.1.0"; "SLUG-VERSION-GST" = "RVS_Generic_Swift_Toolbox: 1.10.1"; "SLUG-VERSION-MB" = "RVS_MaskButton: 1.2.0"; "SLUG-VERSION-PP" = "RVS_Persistent_Prefs: 1.3.1"; "SLUG-VERSION-UKT" = "RVS_UIKit_Toolbox: 1.1.5"; "SLUG-VERSION-WHITEDRAGON" = "White Dragon SDK: 3.2.2"; 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 https://github.com/evgenyneu/keychain-swift
- kelnos 4y agoThe problem I have with adopting something like this is that (other than the added time it would take to write and maintain all my own dependencies), I don't trust myself to avoid writing the same kinds of security bugs that a third-party dependency might also write. But those bugs are much more likely to be discovered and fixed in the widely-used third-party library than in my bespoke library, even if I publish that library as open source. Sure, I would never write these log4j security-related bugs, because I would never even think to write such obscure functionality into a logging library for my own use. Regardless: frankly, I think anyone who claims they won't write security bugs... well, that kind of person is probably a bit unrealistic about the flawlessness of own abilities, to put it as politely as possible.
- ChrisMarshallNY 4y agoI don't claim to "never write security bugs." However, it appears that the norm in the industry, is to write lash-up code, as quickly as possible, in the hopes on an MVP that will get brought up by a FAANG. And I am doubtful that most OSS actually gets all that "other eyeballs vetting" that everyone talks about. Most folks that I know, that use a lot of these dependencies, would be unable to understand what goes on in them, let alone offer fixes. In fact, I remember a founder, on this very forum, declare that "If you don't get physically sick, looking at your MVP code, then you are spending too much time on code quality." That posture doesn't exactly inspire confidence. I'm pretty good at what I do, and I tend to "overengineer" my security-related stuff, because I don't really have huge confidence in that. It's not my forte. But writing good code, is something that I can do. Like I said, WFM. YMMV.
- kelnos 4y ago> I don't claim to "never write security bugs." Sorry if I gave that impression; I wasn't trying to put those words in your mouth. > And I am doubtful that most OSS actually gets all that "other eyeballs vetting" that everyone talks about. Agreed, but a reasonably popular OSS project has a much higher chance of getting that vetting (or any vetting at all, really) than a bespoke library that the public never sees. The chances are a little higher for a nice / little-used bespoke library that you end up putting on GitHub or wherever, but it's still pretty low. > In fact, I remember a founder, on this very forum, declare that "If you don't get physically sick, looking at your MVP code, then you are spending too much time on code quality." I would never want to work for such a founder. I get the tension between getting a MVP out before you run out of money, but experience shows that prototype code ends up living in production a lot longer than anyone plans for. And I've personally seen those prototypes cause 6 and 7 figures of damage to a company later, when they haven't been properly replaced or at least improved when they should be. I'm glad what you're doing works for you (you sound like you probably actually are an above-average developer, unlike -- by definition -- most people), but I don't think I could in good conscience recommend your approach as a general practice.