Re:'Securing Open Source Software Act' introduced to US Senate
by gus_massa on Friday September 23, 2022 @06:57PM
(#32958049)
>> pull that code in without looking at it
> Is no longer reasonable. The dependency chains are too vast to expect the end-user to be able to audit the whole thing.
Each open source project is different. For example I'm using:
Racket: Only the main distribution that is created by the development team and a few packages, and ver few additional packages, like 1 or 2 for viewing the assembler version of the compiled functions.
Python: Also only the official distribution, NumPy and perhaps 1 or 2 more packages. The batteries are included, so it's not necessary to download too much.
LaTeX: As many packages as I can add, my coworkers hate me. Each package has a different author and chains to more and more packages. But I'm using MiKTeX and I thrust the maintainer whoever he is [1]
[1] I had to google the name of the maintainer. He is Christian Schenk, I was convinced his name was Michael or something like that.
> Is no longer reasonable. The dependency chains are too vast to expect the end-user to be able to audit the whole thing.
Each open source project is different. For example I'm using:
Racket: Only the main distribution that is created by the development team and a few packages, and ver few additional packages, like 1 or 2 for viewing the assembler version of the compiled functions.
Python: Also only the official distribution, NumPy and perhaps 1 or 2 more packages. The batteries are included, so it's not necessary to download too much.
LaTeX: As many packages as I can add, my coworkers hate me. Each package has a different author and chains to more and more packages. But I'm using MiKTeX and I thrust the maintainer whoever he is [1]
[1] I had to google the name of the maintainer. He is Christian Schenk, I was convinced his name was Michael or something like that.