To me, the two major problems are:

  1. no namespaces

Someone uploads “serde2”? that’s blocked forever. Someone uploads a typo version of a popular package? Too bad for you, learn how to type.

  1. the github connection

If you want to contribute to crates.io you’re bound to github. No gitlab, codeberg, gitee, sourcehut, etc.

Not sure if there are any other problems, but those two seem like the biggest things and #1 is AFAIK not something they ever want to change + it would be difficult to as one would need a migration strategy.

  • sugar_in_your_tea@sh.itjust.works
    1·
    1 year ago

    Eh, they could change #1 if they allow current non-namespaced packages but don’t allow new ones. That’s a pretty lazy migration strategy, but they could take it a step further and allow aliases (e.g. serde can be namespace/serde, and that’s set on the serde package).

    But the bigger issue is that the devs don’t want to support namespaces.

    #2 is the stronger argument imo. A package manager should not rely on a single external source.

  • verstra@programming.dev
    1·
    1 year ago

    Isn’t github used only as the auth provider? It is not using any git features, just leaning on the security guarantees of github. I don’t find this too alarming.

    If you want, you can use git links when declaring dependencies in Cargo.toml. So alternative to crates.io is basically any git host already!

    • onlinepersona@programming.devOPEnglish
      1·
      1 year ago

      Isn’t github used only as the auth provider?

      Still makes you bound to github. Can’t publish to crates.io without github.

      just leaning on the security guarantees of github

      What security guarantee does github have? I can create a new account right now with a random email, sign up for crates.io and type-squat a package.

      If you want, you can use git links when declaring dependencies in Cargo.toml. So alternative to crates.io is basically any git host already!

      Sure, but how do you discover the package? That’s the other function of a registry. Also, I could easily just add another package as a submodule, but that’s not the point.

    • anlumo@feddit.de
      1·
      1 year ago

      Semver checks don’t work with straight git urls, since you can only link to an explicit branch or commit, not a version.

      • BB_C@programming.dev
        1·
        1 year ago

        version can be passed with git actually. And it will need to match with the version set in Cargo.toml from the git source.

        I wouldn’t call that an alternative to crate registries though (of which, crates.io is only one impl).

        Also tangentially related, cargo-vendor is a thing.

        • anlumo@feddit.deEnglish
          1·
          1 year ago

          Semver strings allows stuff like “version 2.5.x, but below 2.5.6”. Then cargo calculates the best solution for satisfying all dependency specifications from all packages using a single version (if possible).

          Specifying a version in addition to the git branch doesn’t help there at all, because you still have to do it manually then.

  • TechNom (nobody)@programming.devEnglish
    1·
    1 year ago

    While I don’t want to deny the problems of not having namespaces, they will introduce a new set of problems. One issue with Github and similar platforms with namespaces is that a search for a repo turns up multiple projects with the same name under different namespaces. It’s always a confusion as to which one is canonical. Another problem is that people are now going to name squat namespaces instead of project names. Imagine somebody registers the serde namespace. Their crates may be mistaken as the canonical one.

  • SavvyWolf@pawb.socialEnglish
    1·
    1 year ago

    If Github isn’t used for source control, why on earth is it the only auth provider?

    Why has crates.io given Microsoft the ability to control who can and cannot publish Rust code?

    Namespacing is whatever, but IMO the real issue is the disproportionate and unnecessary amount of power given to a company known for pushing monopolies.

    • BB_C@programming.dev
      1·
      1 year ago
      • GitHub wasn’t always owned by Microsoft. At least get your dates right.
      • Yes, GH shouldn’t be the sole auth provider.
  • Turun@feddit.de
    0·
    1 year ago

    I know a lot of people want namespaces. And I think it would be nice for a bigger project to have an obvious way to show which packages are part of this big project, and which are not. For example the different serde serialization formats would not need to be listed in the docs, but simply be present in one single serde-formats namespaces.

    It it does fuck all for type squatting. Sure, now I’m safe from getting malicious code by doing tokio/tokiu-http, but tokiu/tokio-http can still be malicious!

    The only solution to type squatting would be a checksum. So instead of adding Tokio to your toml file you’d have to add e.g. tokio-fld, with the fld part being some kind of check that is derived from the name. Similar to a hash, all names that are similar to tokio would get a wildly different suffix.

    • sugar_in_your_tea@sh.itjust.works
      0·
      1 year ago

      I think you could get it with a signature, just like with Linux repos. Basically, the org would sign the metadata so you know it came from that org’s key.

      That way you’d need both a malicious name and access to the key. You don’t need the suffix here, just a section in the toml that lets you list keys per org, and if it changes, you’d get prompted to update it.

      • Turun@feddit.de
        0·
        1 year ago

        I don’t think changing is the problem, incorrect initial entry is the problem. Linux has centralized package maintainers, cargo does not (or am I wrong?)

        Or do you mean that adding a namespace would require a key and then all crates in that namespace are unlocked? Then only the initial cargo add would be dangerous, all subsequent ones in the same namespace would not require manual confirmation.