Skip to content

[TSC] choose a npm publication method for the future #87

Open

Description

@UlisesGascon

We started a discussion around the idea of using Trusted Publishing (ref), this issue is a more formal continuation of my comment:

Regarding trusted Publishing we did a great research and concluded that:

We believe Trusted Publishing represents the future, but it’s not yet ready for adoption in critical projects, as in its current state it wouldn’t prevent attacks such as Shai-Hulud and other recent ones.
https://openjsf.org/blog/publishing-securely-on-npm

Mostly due the missing step for 2FA confirming the publication. This will be fixed by npm once staged publishing is deployed (no ETA yet): https://github.blog/security/supply-chain-security/strengthening-supply-chain-security-preparing-for-the-next-malware-campaign/

In Express we are trying to do a CI version with 2FA (under discussion: expressjs/discussions#443), so we can probably adopt it if we want to avoid local publication due bus factor

cc: @webpack/security-wg

Next steps

  • Include TSC Meeting agenda label

Context

Activity

  1. evenstensberg commented on Jul 13, 2026

    @evenstensberg
    Member

    status:

    1. try out on a seperate repo
    2. Discuss how it went and see if we want to add this org wide.
  2. UlisesGascon commented on Jul 13, 2026

    @UlisesGascon
    MemberAuthor

    Probably this will help us to decide: openjs-foundation/security-wg#339 👍

  3. bjohansebas commented on Jul 13, 2026

    @bjohansebas
    Member

    My two cents: I recently enabled this for raw-body, and compared to webpack's current workflow, it only adds one extra step: logging into npm and approving the publish request with 2FA.

    It really depends on who is doing the release and from where. Right now, you can merge a PR from your phone and trigger a release. With this change, you'd also need to log into npm, complete the 2FA, and approve the publish request.

  4. evenstensberg commented on Aug 10, 2026

    @evenstensberg
    Member
  5. evenstensberg commented on Sep 7, 2026

    @evenstensberg
    Member

    Status

    • @alexander-akait will try it out on coffee-loader when he has time
    • @UlisesGascon provides help if needed
    • Looking at token policies after implementation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions