this post was submitted on 23 Apr 2026
502 points (99.6% liked)

Selfhosted

58725 readers
939 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] delcaran@feddit.it 6 points 10 hours ago (3 children)

It's not, it's a problem of every package manager that do not use sources and checksums, like rust and python. Take a look at this article that does a better job then me at explaining the situation.

[–] AnarchistArtificer@slrpnk.net 1 points 18 minutes ago

Thanks for the link. There have been a few people in this thread making this point, and I was considering asking them to elaborate so that I can gauge what my risk is from using pip for python. I appreciate you providing a resource so I can go learn more about this

[–] arcterus@piefed.blahaj.zone 5 points 6 hours ago* (last edited 6 hours ago)

In a recent analysis, Adam Harvey found that among the 999 most popular crates on crates.io, around 17% contained code that do not match their code repository.

17%!

Let me rephrase this, 17% of the most popular Rust packages contain code that virtually nobody knows what it does (I can't imagine about the long tail which receives less attention).

Given that he lied about the results of the analysis he is using to prove his point, I find it hard to trust anything in this article.

In the analysis, Harvey said only 8 repositories did not match their upstream repos. The other problems were issues like not including the VCS info, squashing history, etc.

EDIT: Also, I just noticed that he called it a "recent" analysis. It's roughly a two year old analysis. I expect things have improved a bit since then, especially since part of the problem was packaging using older versions of Cargo.

[–] anyhow2503@lemmy.world 5 points 9 hours ago (1 children)

The good news is that there already is a gold standard for supply chain security: the Go programming language.

Lmfao

[–] bright_side_@piefed.world 4 points 7 hours ago (1 children)

Competent standard lib + decentralized libs + checksum db.

While the article is a bit theatralic, it offers important arguments.

[–] anyhow2503@lemmy.world 1 points 58 minutes ago

There are some good points in it, though I wouldn't really consider go dependencies all that decentralized in practice and I don't understand how checksum db will protect against supply chain attacks with stolen credentials, but I admit I haven't looked into the details.