Skip to content
Founder Tools

NewsDeveloper tools

StepSecurity opens its package registry to open-source teams

With a $20 million Series A, StepSecurity introduced a free registry for JavaScript projects on GitHub. Here’s which builds qualify and what the two-day waiting period changes.

What the free tier covers at launch
Repositories
Public on GitHub
Build environment
GitHub-hosted runners
Package managers
npm, pnpm and Bun
Default cooldown
Two days

StepSecurity describes this as the first release. Its community-tier documentation lists the current limits.[2][3]

What this means for founders

  • The free tier covers public repositories using Harden-Runner on GitHub-hosted runners. Private repositories and self-hosted runners require the enterprise tier.
  • Teams can put a waiting period on new dependency versions. StepSecurity sets the default at two days.
  • For a startup that publishes an open-source SDK, the release offers a way to test package controls on the same builds its contributors use.

A new choice for public JavaScript projects

StepSecurity announced a $20 million Series A led by Elephant on November 18. It also opened a free version of Secure Registry, a service previously available to enterprise customers. The registry checks packages requested during an automated build and records the outcome in the build’s run insights.

An open-source team can use the free tier for public repositories that run Harden-Runner on GitHub-hosted infrastructure. The first release supports npm, pnpm and Bun. That distinction matters for a startup with a public SDK and a private application. Their repositories can sit in the same organization and still qualify for different plans.

Sources12

How a two-day wait changes release day

A maintainer preparing a release can now see which dependency requests the registry allowed or blocked. One control delays newly published package versions for two days by default, giving maintainers time to learn about problems after publication. Another blocks versions the service has identified as compromised.

Consider an SDK that needs an upstream bug fix published this morning. The team now has a release-planning decision. Can customers wait two days? Who can review an urgent exception? Trying the policy on an ordinary SDK build gives maintainers a chance to answer both questions before a customer is waiting for a fix.

Sources23

Sources

3 references