Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Move to NPM trusted publishing

Open
#55 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, node.js

Research direction

Read the issue references, especially the deck.gl-raster .github/workflows/release.yml example, then locate the package publishing workflow in stac-react. Compare the current token-based setup with trusted publishing and verify that publishing no longer depends on a token and still completes successfully.

Written by the indexing model from the issue text.

Description

As supply chain attacks get worse, we want to move our packages to be published only by trusted publishing.

This package is currently allowed to publish by token.

See https://github.com/developmentseed/how/issues/475 and see https://github.com/developmentseed/deck.gl-raster/blob/main/.github/workflows/release.yml for an example of trusted publishing. Also ref https://github.com/developmentseed/deck.gl-healpix/issues/6

Dominant language
TypeScript
Stars
34
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from developmentseed/stac-react

All issues in developmentseed/stac-react

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.