StepSecurity Adds Free Secure Registry Tier for Harden-Runner Workflows

· Original article ↗

Summary

StepSecurity made its Secure Registry free for qualifying public GitHub repositories and integrated it with Harden-Runner, adding a two-day npm release cooldown, blocking known compromised packages, and workflow-level package insights.

Key points

  • The free tier is for public repositories using GitHub-hosted runners with the Harden-Runner GitHub Action; private repositories and self-hosted runners require the enterprise tier.
  • Setting secure-registry: true configures supported package managers to use the registry in GitHub Actions; the initial release supports npm, pnpm, and Bun.
  • Default protections delay newly published versions for two days and block packages identified as compromised.
  • A sample workflow allowed an ordinary dependency, blocked a TypeScript release within the cooldown, and blocked Chalk 5.6.1 as a known compromised package.
  • Harden-Runner Insights records package requests, decisions, and reasons, helping users verify whether downloads went through the secure registry.
  • Cached dependencies are not checked, and some Yarn workflows may bypass the registry; if the registry is unavailable, installs fail rather than skipping checks.

Article Details

Event Type
StepSecurity made its Secure Registry available in a free community tier and integrated it with Harden-Runner for GitHub Actions.
Impact
The registry applies a default two-day cooldown to newly published package versions and blocks versions identified as compromised. The article demonstrates those controls blocking a newly published TypeScript release and a compromised Chalk release with HTTP 403 responses. The offering is free for public repositories using GitHub-hosted runners; private repositories and self-hosted runners require the enterprise tier.

Vendors

Products

Countries

Related Articles