Live data from Hacker News

Open source projects could sell SBOM fragments

thomas-huehn.com

21–30 of 64 posts

Re: Open source projects could sell SBOM fragments

#22
post #2

This doesn't make much sense to me. Why would someone want to pay each and every open source project to see the SBoM when they could pay a single provider or use an open source tool to get that info for all of their dependencies?

For private usage no one gives a shit about SBOM, but for enterprise usage it's absolutely required.

Which is why enterprises everywhere has software and tooling in place to provide this, for the exact things they do deliver.

I don’t see how anyone can «sell» this information when it’s literally available for free already.

Re: Open source projects could sell SBOM fragments

#24
Some of the demand will disappear, when, instead of adding a dependency on an open source package, to get that function you want, you use your LLM "assistant".

(The assistant will effectively plagiarize open source code, and then you don't have a dependency, and you slap your own copyright notice on it.)

LLM-generated/laundered code could move code bases a little bit back in the direction of low-dependency monoliths, like a lot of software was before the wild popularity of open source code (and, especially, modern Web dev).

Re: Open source projects could sell SBOM fragments

#25

Earlier quoted context omitted.

For private usage no one gives a shit about SBOM, but for enterprise usage it's absolutely required.

Enterprise also doesn't really care. It is just another box to tick and an excel sheet to fill out, correctness isn't actually required. You just need something to put in the list, so you may as well purchase something wrong but authoritative-looking in bulk.

It might be required and audited for software deployed to / interacting with government cloud. Eventually it will have to be correct too, as otherwise would be a security risk.

Re: Open source projects could sell SBOM fragments

#26
post #24

Some of the demand will disappear, when, instead of adding a dependency on an open source package, to get that function you want, you use your LLM "assistant". (The assistant will effectively plagiarize open source code, and then you don't have a dependency, and you slap your own copyright notice on it.) LLM-generated/laundered code could move code bases a little bit back in the direction of low-dependency monoliths,…

This is a genuine concern, especially now that managers discovered that "llm assistence 10x-es developer productivity". (Where kLoCs are a measure of productivity and a world with more code is an obvious, axiomatic good).

Re: Open source projects could sell SBOM fragments

#27
post #14

You downloaded it without knowing the license (or trusting your download tool to tell you correctly) and the solution is to pay a third-party?

Yes, that's the state of the art unfortunately. There are a number of vendors who can scan your source code and generate a list of FOSS libraries with licensing info (SBOMs). If we can find a way to get this money flowing to our fellow FOSS devs, that would be a huge win for the community.

Re: Open source projects could sell SBOM fragments

#28

Earlier quoted context omitted.

For private usage no one gives a shit about SBOM, but for enterprise usage it's absolutely required.

Which is why enterprises everywhere has software and tooling in place to provide this, for the exact things they do deliver. I don’t see how anyone can «sell» this information when it’s literally available for free already.

> I don’t see how anyone can «sell» this information when it’s literally available for free already.

I think this has been repeated thousands of times in history.

Re: Open source projects could sell SBOM fragments

#30

The providence of the SBOM is important. If you can't say "I made this" in reference to the SBOM then it's pretty much worthless. Or, flip the script, if you're concerned enough about supply chain security to mandate an SBOM, you probably don't trust the supplier anyway. There's the "but I signed it" crowd, but the wheels fall off when they've signed compromised artifacts too. I just don't see a scenario where an SBO…

It's not so much about who made what. It's about knowing what versions where used and which CVEs are attached.
Post reply on HN