“someone uploaded ~3500 packages to PyPI that point to a malicious URL”

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
  • support

    Issue tracker for support requests related to using https://pypi.org (by pypi)

  • https://github.com/pypa/pypi-support/issues/923

    "The package only contains __init__.py file, that says:

    # the purpose is to make everyone pay attention to software supply chain attacks, because the risks are too great."

  • cupy

    NumPy & SciPy for GPU

  • https://github.com/cupy/cupy/issues/4787

    Salient points being that cupy releases a new named package for each cuda version, so future package names are of course predictable. Since PyPi doesn’t allow namespacing, cupy’s plan is to register new names ASAP when cuda releases a new version and monitor and report other packages purporting to be cupy that get uploaded.

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

    SurveyJS logo
  • LavaMoat

    tools for sandboxing your dependency graph

  • > Not sure how we could fix it without slowing way down and doing a lot more work.

    You restrict what your dependencies can do in the first place, so that if they're malicious (or just buggy the) scope of what they can do is limited. This doesn't eliminate the risk entirely; after all, it's possible for a library to introduce vulnerabilities just by doing its job incorrectly; but it massively limits the scope of what you'd need to audit. Right now, any dependency can do anything, so you'd need to audit all of them.

    See POLA Would Have Prevented the Event-Stream Incident[0] for more explanation and LavaMoat[1] for an example of tooling that's trying to tackle this problem.

    [0] https://medium.com/agoric/pola-would-have-prevented-the-even...

    [1] https://github.com/LavaMoat/lavamoat

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • CuPy: NumPy and SciPy for GPU

    1 project | news.ycombinator.com | 28 Nov 2023
  • Fedora 40 Eyes Dropping Gnome X11 Session Support

    1 project | news.ycombinator.com | 20 Sep 2023
  • How does one optimize their functions?

    1 project | /r/AskComputerScience | 13 Jun 2023
  • Speed Up Your Physics Simulations (250x Faster Than NumPy) Using PyTorch. Episode 1: The Boltzmann Distribution

    1 project | /r/Physics | 13 Apr 2023
  • ELI5: Why doesn't numpy work on GPUs?

    1 project | /r/learnpython | 31 Jan 2023