From 4df807b9875bd36019fc2bc408add0d2636b43c1 Mon Sep 17 00:00:00 2001
From: nishantms <nishantms@github.com>
Date: Tue, 11 Aug 2026 12:51:48 -0400
Subject: [PATCH] remove the package version status 403 response

---
 api/registry.npmjs.com/package-version-status.yaml | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/api/registry.npmjs.com/package-version-status.yaml b/api/registry.npmjs.com/package-version-status.yaml
index 07a50cd..428fa4f 100644
--- a/api/registry.npmjs.com/package-version-status.yaml
+++ b/api/registry.npmjs.com/package-version-status.yaml
@@ -50,8 +50,6 @@ paths:
           $ref: "#/components/responses/PackageVersionStatusBadRequest"
         "401":
           $ref: "#/components/responses/PackageVersionStatusUnauthorized"
-        "403":
-          $ref: "#/components/responses/PackageVersionStatusForbidden"
         "404":
           $ref: "#/components/responses/PackageVersionStatusNotFound"
         "429":
@@ -107,16 +105,6 @@ components:
             properties:
               error:
                 type: string
-    PackageVersionStatusForbidden:
-      description: |
-        Package version status is not enabled for this package. This is the rollout gate only. Not having access to a package is reported as `404`, not here.
-      content:
-        application/json:
-          schema:
-            type: object
-            properties:
-              error:
-                type: string
     PackageVersionStatusNotFound:
       description: |
         The package version does not exist, or the authenticated user cannot read it. These are deliberately indistinguishable so the response does not reveal whether a package the caller cannot see exists.