• Kairos@lemmy.today
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 hours ago

    There’s a lot of features that make it a better package manager but nobody cares. Every project has hundreds of dependencies and packages use a minimum, not exact, version.

    • LurkingLuddite@piefed.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      8 hours ago

      That sounds more like bad practices from the community. It definitely has ways to use exact versions. Not the least of which the lock file. Or the shrinkwrap file which public packages should be using.

      • dustyData@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        7 hours ago

        Any security system based on expecting good behavior from people is sure to fail. If NPM has no estructural features to enforce safe behaviors, it is vulnerable by default. As no person using it will apply safe practices unless forced to. Specially if the default, easiest, less friction behavior, is inherently unsafe.

        • LurkingLuddite@piefed.social
          link
          fedilink
          English
          arrow-up
          1
          ·
          6 hours ago

          I wouldn’t say pulling in higher versions is unsafe unless an attack like this succeeds. Otherwise it’s only an annoyance.

      • Serinus@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        7 hours ago

        Then you’re waiting forever on vulnerability patches. Especially if there are layers, and each layer waits to update.