Skip to content

Adopt Trusted Publishing and Supply Chain Security Best Practices #2887

Closed

Description

@AdnaneKhan

As I’m sure you may be aware GitHub recently announced changes to NPM publishing (https://github.blog/changelog/2025-09-29-strengthening-npm-security-important-changes-to-authentication-and-token-management/) and is encouraging projects to switch to trusted publishing as soon as they are able.

OpenCode currently uses a long-lived NPM token for publishing and does not leverage basic features such as branch protection for the default branch.

Can OpenCode adopt these measures to protect downstream users?

Activity

  1. rekram1-node commented on Oct 1, 2025

    @rekram1-node
    Contributor

    makes sense

  2. thdxr commented on Mar 25, 2026

    @thdxr
    Member

    To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions