this post was submitted on 02 Apr 2026
156 points (99.4% liked)

Programming

26369 readers
161 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
156
Every dependency you add is a supply chain attack waiting to happen (benhoyt.com)
submitted 3 days ago by codeinabox@programming.dev to c/programming@programming.dev
24 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] MonkderVierte@lemmy.zip 8 points 2 days ago (3 children)

Soo, how do i build Rust packages without Cargo?

[–] TehPers@beehaw.org 5 points 2 days ago (2 children)

You can run rustc directly! You just need to pass about 30 different parameters to it as well as a list of all the dependencies you use and...

Look, it works for small projects.

[–] FizzyOrange@programming.dev 1 points 1 day ago (1 children)

The only reason to do this is if you're directly integrated Rust into an existing build system (e.g. Bazel). It's not going to help with this problem at all.

[–] TehPers@beehaw.org 2 points 1 day ago

No, it wont. I wasn't suggesting someone should use rustc directly. You're already using Rust, so using cargo isn't adding to the supply chain.

That being said, there was one time I needed to use rustc directly. We had an assignment that needed to be compilable from a single source file. I couldn't bundle a Cargo.toml, so I gave a build script that used rustc directly.

[–] MonkderVierte@lemmy.zip 2 points 2 days ago (1 children)

So i could theoretically script a wrapper?

[–] TehPers@beehaw.org 5 points 2 days ago

I don't see why not. Cargo is fundamentally just a fancy wrapper around rustc, anyway. Sure, it's a really fancy wrapper that does a lot of stuff but it's entirely possible to just call rustc yourself.

[–] BB_C@programming.dev 2 points 1 day ago (1 children)

Why do you think cargo is a problem?

[–] MonkderVierte@lemmy.zip 3 points 1 day ago* (last edited 1 day ago) (1 children)

Not cargo per se, but even the tutorial for a cli-tool is like "setup clap, which has 20 dependencies and a kitchen sink". The whole (cargo-centric) ecosystem is much like Node, with the same problems.

And also, cargo.toml has inconsistencies and double-standards.

[–] BB_C@programming.dev 2 points 1 day ago* (last edited 1 day ago) (1 children)

Not cargo per se, but even the tutorial for a cli-tool is like “setup clap, which has 20 dependencies and a kitchen sink”. The whole (cargo-centric) ecosystem is much like Node, with the same problems.

cargo new with-clap
cd with-clap
cargo add clap --no-default-features

% cargo tree
with-clap v0.1.0 (/tmp/with-clap)
└── clap v4.6.0
    └── clap_builder v4.6.0
        ├── anstyle v1.0.14
        └── clap_lex v1.1.0

And also, cargo.toml has inconsistencies and double-standards.

Can you expand on that?

[–] MonkderVierte@lemmy.zip 1 points 4 hours ago

--no-default-features

That's cheating!