Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

NodeBB

  1. Home
  2. uncategorized
  3. I wonder if we get a response from NPM on all the package compromises at some point + what their idea is to mitigate those.

I wonder if we get a response from NPM on all the package compromises at some point + what their idea is to mitigate those.

Scheduled Pinned Locked Moved uncategorized
3 Posts 2 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • pixel@desu.socialP This user is from outside of this forum
    pixel@desu.socialP This user is from outside of this forum
    pixel@desu.social
    wrote last edited by
    #1

    I wonder if we get a response from NPM on all the package compromises at some point + what their idea is to mitigate those.

    marcusschwemer@muenchen.socialM 1 Reply Last reply
    0
    • pixel@desu.socialP pixel@desu.social

      I wonder if we get a response from NPM on all the package compromises at some point + what their idea is to mitigate those.

      marcusschwemer@muenchen.socialM This user is from outside of this forum
      marcusschwemer@muenchen.socialM This user is from outside of this forum
      marcusschwemer@muenchen.social
      wrote last edited by
      #2

      @pixel Is it really a npm issue? If package maintainers do not pay enough attention to their dependencies, this could happen with composer and other dependency managers also. IMHO

      pixel@desu.socialP 1 Reply Last reply
      0
      • marcusschwemer@muenchen.socialM marcusschwemer@muenchen.social

        @pixel Is it really a npm issue? If package maintainers do not pay enough attention to their dependencies, this could happen with composer and other dependency managers also. IMHO

        pixel@desu.socialP This user is from outside of this forum
        pixel@desu.socialP This user is from outside of this forum
        pixel@desu.social
        wrote last edited by
        #3

        @MarcusSchwemer the thing is: if it happens this often, the service provider should step in with mitigations as well.

        Just "it's the maintainers fault" doesn't work if millions of users (and systems) are at stake.

        Adding a third factor, like signatures etc. is probably what's next.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups