Is it possible to have multiple packages in the dependents view of a repo ?

[pietrozullo]

Select Topic Area

Question

Body

I would like to have all the packages contained in my repo in this dropdown view and also have all the dependents of my packages listed here. Is that possible ?

I know that nextjs made it happen

Thanks in advance for anybody that can help :) 🤗

[INikolOFF]

Generally no, GitHub does not allow you to manually populate the package dropdown or automatically list all dependents unless your project meets the requirements of the GitHub Dependency Graph.You cannot manually add packages to this dropdown.
If GitHub doesn’t detect your ecosystem, it simply won’t show anything.If your package is internal, private, unpublished, or not in a supported ecosystem, dependents will not appear. GitHub does not provide a way to force dependents to show manually.

[pietrozullo]

Thanks! I already have the repository entry in my package.json lines but it seems to not be working (not showing the package in my repo), I will try to add the directory entry too and see if this solves it.
Refs: https://docs.npmjs.com/cli/v11/configuring-npm/package-json

[INikolOFF]

GitHub doesn’t automatically detect or show your npm package, even if your package.json has a repository field.

Check that the repository URL is correct
It must be the full Git URL:

"repository": {
  "type": "git",
  "url": "https://github.com/USERNAME/REPO.git"
}

Create a GitHub Release with the same version as your npm package.
Example: if npm has 1.2.0, make a release tag v1.2.0.
→ After this, GitHub will automatically link your npm package on the repo page.

I hope this solve your case.

[INikolOFF]

Make sure repository.url is EXACTLY like this

.git and include https://:

Make sure your Git tag MATCHES your npm version

Make sure your npm package actually contains the repo link

I'm sure one of these 3 steps is 100% the issue

[pietrozullo]

I did the steps, I guess this could take some time to update. but I am confused by the idea that setting an arbitrary version in the github release will help.

Example: if npm has 1.2.0, make a release tag v1.2.0.

I will wait a couple days to see if this comes up, I will update here.

[pietrozullo]

I have done all this and the packages are still not showing up :(
Can you maybe check, this is all public, if you see some problem ?
https://github.com/mcp-use/mcp-use

[chumarhassan]

Hey! 😊

What you’re asking about – having a dropdown that lists all packages in your repo and their dependents – is not something GitHub does automatically. Next.js looks like it does it, but that’s actually a custom feature on their website, not part of GitHub itself. They get it by reading their packages and querying the npm registry.

Here’s how you can do something similar:

1. List all packages in your repo

If you use a monorepo, these commands can show all your packages:

npm workspaces: npm workspaces list

Yarn workspaces: yarn workspaces list

pnpm workspaces: pnpm -w list

Lerna: lerna list

Turborepo: turbo ls

This gives you a list of every package in your repo.

2. Find which packages depend on each other

You can use:

npm ls

or to see the full dependency tree:

npm ls --all

This will show which packages are dependent on others.

3. Use GitHub’s Dependency Graph

GitHub has a built-in dependency graph, which you can enable under:
Settings → Code security and analysis → Dependency graph

It shows dependencies and dependents for your repo, but it doesn’t create a dropdown like Next.js.

4. Make a dropdown like Next.js

If you want the same dropdown style, you need to create it yourself:

Read all package.json files in your repo

Extract package names and dependencies

Render a dropdown in your website or documentation

Example script:

import fg from "fast-glob";
import fs from "fs";

const packages = fg.sync("packages/**/package.json").map(path => {
const pkg = JSON.parse(fs.readFileSync(path, "utf8"));
return {
name: pkg.name,
version: pkg.version,
deps: Object.keys(pkg.dependencies ?? {}),
};
});

console.log(packages);

This will give you all packages and their dependencies, which you can show in a dropdown.

[pietrozullo]

manifest files are public

Which manifest files ?

[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! 💬

[Shreyas-S-809]

Yes.

The Dependents tab doesn’t represent one package — it represents everything published from that repository.

If your repo publishes multiple packages (for example a monorepo like packages/core, packages/react, packages/cli), GitHub aggregates all of them and shows:

• repos that depend on any of those packages
• packages depending on any of them

So the view is repo-level, not package-level.

If you want separation, each package needs its own repository (or its own GitHub package namespace).