Streamline OIDC setup for large monorepos/organizations with many NPM packages

[keller-mark]

Select Topic Area

Product Feedback

Body

I have a large monorepo that contains 54 NPM packages in the same NPM organization (@vitessce, https://www.npmjs.com/search?q=%40vitessce )

I need to set up OIDC publishing for all 54 packages in the organization. Currently, this requires me to manually do the following for each individual package (all are in the same repo and specify the same .yml workflow file):

• Navigate to its page https://www.npmjs.com/package/@vitessce/workers
• Click Settings https://www.npmjs.com/package/@vitessce/workers/access
• Click the "Github Actions" button under "Trusted Publisher" "Select your publisher"
• Type into 4 text inputs (organization, repo, yml filename, environment name)
• Click Save Changes button
• Click Use security key button
• Click my password manager button

This is extremely time consuming. And now i will need to do the same whenever my monorepo expands to define a new package.

A streamlined workflow for NPM organizations is urgently needed. At minimum, it should reduce the number of clicks for such repetitive actions. Ideally, we could configure OIDC publishing for any package (current or future) within the NPM organization using the same settings (same github repo and .yml actions workflow file and environment name).

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[omercnet]

we need an org level trusted publishing, not just package level

[czy88840616]

I have the same issue. Our organization uses a monorepo to manage projects and previously used Lerna for publishing. Even after migrating to Trusted Publishing, we still need to add the configuration for each package individually, which is almost an unsustainable amount of work.

[slinkydeveloper]

We're facing the same issue and this slows down the adoption path to trusted publishing.

[MasteraSnackin]

I completely agree with the concerns raised here. The current OIDC setup process for monorepos is a significant pain point that affects many organizations.

The Core Issue

As @omercnet pointed out, what we really need is organization-level trusted publishing, not just package-level configuration. The current approach forces us to repeat the same configuration (GitHub repo, workflow file, environment name) for every single package, which becomes increasingly unsustainable as monorepos grow.

Real-World Impact

As mentioned by @czy88840616 and @slinkydeveloper, this manual overhead is actively slowing down the adoption of trusted publishing. For organizations managing dozens or even hundreds of packages from a single monorepo (like your 54 packages), the current workflow is impractical. The time spent on repetitive configuration could be better used for actual development work.

Proposed Solutions

1. Organization-level OIDC configuration: Allow NPM organizations to set default trusted publisher settings that automatically apply to all packages (current and future) within that organization

2. Wildcard/pattern-based package matching: Support patterns like @orgname/* to configure OIDC for all packages under an organization scope in one go

3. Bulk configuration API: Provide a programmatic way to configure OIDC settings for multiple packages simultaneously

4. Inheritance model: Let individual packages inherit OIDC settings from the organization level, with the option to override when needed

Business Case

Trusted publishing is the more secure approach that NPM is encouraging everyone to adopt. However, if the barrier to entry remains this high for monorepo users, it actually works against security adoption. Making this process more efficient would:

• Accelerate trusted publishing adoption
• Reduce configuration errors from repetitive manual entry
• Support modern development practices (monorepos are increasingly common)
• Lower maintenance burden when repository or workflow details change

I hope the NPM/GitHub team can prioritize this enhancement. It would make a significant difference for the developer experience.