How to remove not listed packages and versions

[phongkhuu115]

Select Topic Area

Question

Body

I published a package, but it doesn't link to a repository; instead, it is linked to an organization. Although I don't see that package listed on the organization packages page

I can see the package information using npm view <@org>/<package-name>. But I can't see that package listed anywhere.

I wonder how to delete that package?

[Fleurdelys0]

Hello,

You can delete packages using terminal.

If you aren't already logged in, run:
npm login

Unpublish the package:
To remove the entire package, run the following command. The --force flag is required to bypass the confirmation prompt.
npm unpublish <@org>/<package-name> --force

To remove only a specific version, use:
npm unpublish <@org>/<package-name>@<version>

[phongkhuu115]

@Fleurdelys0 Hi, thanks for the reply. I forgot to mention that I published to GitHub Packages Registry. I tried the npm unpublish command, and it tells me Package deletion from the command line is disabled in GitHub Package Registry.

[Fleurdelys0]

@Fleurdelys0 Hi, thanks for the reply. I forgot to mention that I published to GitHub Packages Registry. I tried the npm unpublish command, and it tells me Package deletion from the command line is disabled in GitHub Package Registry.

Oh I see,
In this case do you have admin permissions for your repository or organization?

[Satyam6024]

This usually occurs because:

1. The package was published without repository metadata (package.json lacks the repository field),
2. You might not have proper access (only the publishing account can delete it),
3. Or the package is private or unlisted.

Steps to Delete the Package

1. First, make sure you're logged in with the same npm account that published the package:

npm whoami
npm access ls-packages your-npm-username

2. If you're the publisher or have the right permissions:

• To delete a single version:

npm unpublish @org/[email protected]

• To delete the entire package:

You can only do this within 72 hours of publishing unless it's a scoped/private package.

npm unpublish @org/package-name --force

⚠️ --force is required for full package deletion
⚠️ You must be the owner of the package or org admin

3. If You Don’t Have Access
   If the package isn't in your visible org dashboard and you can't unpublish:

• Contact npm support: https://www.npmjs.com/support
• Include:

• Your npm username
• Organization name
• Package name (@org/package-name)
• Reason for removal

They can transfer, deprecate, or delete the package manually.

✅ Bonus Tips

• In future, always include this in your package.json:

"repository": {
  "type": "git",
  "url": "https://github.com/your-org/your-repo.git"
}

• Add "publishConfig": { "access": "public" } if needed.
• Run npm whoami and npm config get registry before publishing to be sure you're authenticated correctly.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[seamusrobertmurphy]

Hi @phongkhuu115,

I think that previous response by @Satyam6024 covers the key fixes, but some details missing regarding the GitHub web deletion method. It may be possible to delete via GitHub Web Interface, which often works when CLI deletion is disabled and packages aren't visible in standard listings.

• Go to organization page → Packages tab (may be in "More" dropdown)
• If not visible, try direct URL: github.com/orgs/YOUR-ORG/packages
• Click package name → Package settings → Delete package

If the package is still missing, then:
• Check personal packages: github.com/users/YOUR-USERNAME/packages
• Package might be under personal account despite org scope

For GitHub Packages Registry, contact [GitHub Support](https://support.github.com/contact), not npm support as mentioned above.

Resoruces:

• [Managing GitHub Packages - Official Deletion Guide](https://docs.github.com/en/packages/learn-github-packages/deleting-and-restoring-a-package)
• [Package Permissions - Access Requirements](https://docs.github.com/en/packages/learn-github-packages/about-permissions-for-github-packages)

[Omprakash3104]

This is a common issue when publishing scoped packages to npm. The package isn't showing up in the organization's package list because of how npm handles scoped package visibility. Here are several ways to delete the package:

Method 1: Using npm CLI (Recommended)
bash

Delete the package

npm unpublish @your-org/package-name --force

Or if you want to specify a specific version

npm unpublish @your-org/[email protected]
Method 2: If the package is older than 72 hours
If your package was published more than 72 hours ago, you'll need to contact npm support:

Go to npm support

Explain that you need to delete a scoped package that's not visible in your organization

Provide the package name: @your-org/package-name

Method 3: Check package visibility settings
First, verify the package's visibility:

bash
npm view @your-org/package-name
Look for the publishConfig section. The package might be set to private or restricted.

Method 4: Using npm website
Go to npmjs.com

Log in to your account

Check both:

Your personal packages page

The organization's page (even if it's not showing)

Sometimes packages appear under "Packages" tab in organization settings

Prevention for future packages
To ensure proper linking and visibility, add this to your package.json:

json
{
"publishConfig": {
"access": "public"
},
"repository": {
"type": "git",
"url": "https://github.com/your-org/your-repo.git"
}
}
Important Notes:
⚠️ Unpublishing within 72 hours: You can unpublish freely if the package is less than 72 hours old

⚠️ After 72 hours: Requires support intervention to prevent breaking others' dependencies

🔒 Scoped packages: Default to private for paid organizations, which might explain why it's not publicly visible

Try Method 1 first, and if that doesn't work, proceed with contacting npm support via Method 2.