GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Implement PEP-708 - Extend the repository API to mitigate "dependency confusion" attacks · Issue #998 · pulp/pulp_python

Implement PEP-708 - Extend the repository API to mitigate "dependency confusion" attacks #998

New issue
Copy link
New issue
Copy link
Open
#1014
Open
Implement PEP-708 - Extend the repository API to mitigate "dependency confusion" attacks#998
#1014
Copy link
Labels
Feature

Description

@dralley
dralley
opened on Oct 31, 2025
Issue body actions

PEP-708

Dependency confusion attacks, in which a malicious package is installed instead of the one the user expected, are an increasingly common supply chain threat. Most such attacks against Python dependencies, including the recent PyTorch incident, occur with multiple package repositories, where a dependency expected to come from one repository (e.g. a custom index) is installed from another (e.g. PyPI).

To help address this problem, this PEP proposes extending the Simple Repository API to allow repository operators to indicate that a project found on their repository “tracks” a project on different repositories, and allows projects to extend their namespaces across multiple repositories.

These features will allow installers to determine when a project being made available from a particular mix of repositories is expected and should be allowed, and when it is not and should halt the install with an error to protect the user.

Activity

  1. dralley
    added
    Feature
    Triage-Needed
    on Oct 31, 2025
  2. gerrod3
    added 2 commits that reference this issue on Nov 14, 2025

    Implement PEP 708

    This issue will close once commit 04ed021 is merged into the 'main' branch.
    04ed021

    Implement PEP 708

    This issue will close once commit fb1bec8 is merged into the 'main' branch.
    fb1bec8
  3. gerrod3
    added 4 commits that reference this issue on Nov 26, 2025

    Implement PEP 708

    This issue will close once commit 3c6551c is merged into the 'main' branch.
    3c6551c

    Implement PEP 708

    This issue will close once commit d5a660a is merged into the 'main' branch.
    d5a660a

    Implement PEP 708

    This issue will close once commit 29c0f2f is merged into the 'main' branch.
    29c0f2f

    Implement PEP 708

    This issue will close once commit 610ef15 is merged into the 'main' branch.
    610ef15
  4. gerrod3
    removed
    Triage-Needed
    on Mar 23, 2026
  5. gerrod3
    modified the milestone: This milestone has been deleted on Mar 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Feature

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.