StepSecurity Raises $20M for Software Supply Chain Security
A dependency download can decide whether a software release proceeds on schedule. StepSecurity is putting security policy into that moment, alongside the runtime monitoring that helped the Seattle company build an audience among open-source maintainers. A newly published package may have to wait before it enters a build, giving security teams another place to intervene while developers still have work to ship.
StepSecurity announced an oversubscribed $20M Series A on November 18, 2026, led by Elephant, with existing investors Runtime Ventures, Inner Loop Capital and SaaS Ventures participating. The company says the round brings total funding to $23M. CEO and cofounder Varun Sharma and CTO and cofounder Ashish Kurmi plan to expand engineering, security research, sales and marketing while extending protection into additional environments, including agent sandboxes.
The financing arrives with a free Secure Registry community tier integrated into Harden-Runner, StepSecurity's CI/CD security agent. Together, the developments bring a practical enterprise question into focus: how can a security team govern the code entering its development process while keeping that process usable for the people depending on it?
What StepSecurity's Series A finances
StepSecurity's previous financing was a $3M seed announced in May 2024. Runtime Ventures led that round, joined by Inner Loop Capital, SaaS Ventures and DeVC, among others. The latest announcement adds Elephant as Series A lead; DeVC is part of the disclosed seed history, rather than the named participant list for this new round.
The company's current leadership materials identify Sharma and Kurmi as its founders and date the business to 2021. Sharma previously led Microsoft's Azure Security Green Team. Kurmi built Uber's cloud security function and later led infrastructure security at Plaid, experience that places both founders close to the infrastructure and developer workflows their company now sells protection for.
Their origin story includes responding to SolarWinds and Codecov, incidents that exposed how trusted software could become an attacker’s route into development environments. StepSecurity's response has grown from CI/CD protection into a broader set of controls spanning developer machines, repositories and package downloads. The capital supports that expansion, with security research feeding the product work and a larger commercial team expected to bring it to more customers.
Why package downloads need an operating policy
The Secure Registry community documentation describes a hosted service that checks package requests before downloads reach a build. Known compromised versions are refused, and the default cooldown withholds versions published in the previous 2 days. Maintainers can adjust the cooldown and configure exemptions, making the waiting period an explicit policy choice.
The free offering has defined boundaries: public repositories running on GitHub-hosted runners, initially focused on JavaScript package managers including npm, pnpm and Bun. Private repositories and self-hosted runners require the enterprise tier. A buyer evaluating the free product needs to carry those deployment conditions into the evaluation, especially when public projects and private production workflows use different infrastructure.
The launch documentation also explains the operational consequences. Cached dependencies do not pass through a new download check, and an unavailable registry can cause installs to fail. Package policies give a security team authority over part of the delivery process; that team also inherits questions about exceptions, cached artifacts and how engineers recover when a dependency is blocked. Those decisions belong in the rollout conversation, before an urgent build makes them everybody's problem at once.
What runtime evidence adds to the purchase
Harden-Runner's public repository describes monitoring network, file and process activity with context tied to CI/CD workflow execution. That context matters because an operator investigating an outbound connection needs to know which job and process produced it. Network restrictions can then be applied around expected behavior, giving the team a way to move from observing a build to governing its access.
A Chainguard customer account, attributed to Staff Security Engineer Evan Gibler, describes using StepSecurity to establish workflow baselines, limit egress and identify minimum token permissions. The account also explains the alternative work: collecting runner behavior and assembling the infrastructure to analyze it internally. For an enterprise buyer, that is a useful description of the engineering assignment being purchased from a specialist vendor.
Sharma's financing announcement says the company spent its first 2 years building only for public open-source repositories, with results available without a login. StepSecurity reports that more than 20,000 projects now use Harden-Runner's community tier. The commercial significance is inspectability: maintainers can encounter the product in real workflows, and that familiarity can enter an employer's buying process. The company has described that route qualitatively without disclosing a conversion rate from free projects to paid customers.
AI agents widen the deployment assignment
StepSecurity's Dev Machine Guard extends the product conversation onto workstations, inventorying AI coding agents, MCP servers, IDE extensions and packages. The product describes device-level attribution and policy distribution through existing management tools. That is a different deployment relationship from adding a step to a CI/CD job, with endpoint administrators joining the security and engineering teams involved in adoption.
DevCuration's coverage of AI agent runtime security follows an adjacent question about governing agent execution. As AI agents download dependencies and execute code, security coverage has to follow the environment holding those permissions. StepSecurity identifies agent sandboxes as a destination for further product investment. Customers assessing that roadmap should distinguish the controls available for deployment today from the additional environments the Series A is intended to help cover.
The operating relationship keeps expanding with the coverage. A registry policy affects the next install, a runner policy affects the next build, and a workstation policy reaches the person using the development tools. Sharma and Kurmi are adding engineers, researchers and commercial capacity around that sequence, while their customers work out who can approve an exception when the software they need is the package their new security policy has stopped.
Cybersecurity funding, last 30 days
DevCuration's funding database tracked 14 Cybersecurity rounds totaling $909M in disclosed capital over the past 30 days. Recent deals we covered:
- Corma Raises $125M Series A for Defensive CybersecuritySeries A · $125M · Nov 16
- IBM Acquires AuthMind to Expand AI Agent Identity SecurityNov 14
- Finite State Raises $27M Series C for Device SecuritySeries C · $27M · Nov 12
- Vanta Agrees to Acquire Pillar Security for AI GovernanceM&A · $150M (reported by CTech) · Nov 10
- Ballistic Ventures Targets $490M Across Two New FundsFund Target · $490M target · Nov 9
Frequently Asked Questions
How do Secure Registry and Harden-Runner address different parts of a supply chain attack?
Secure Registry applies policy before package downloads reach a build, including cooldowns and blocking known compromised versions. Harden-Runner monitors network, file and process behavior during CI/CD execution. A package passing a download check can still require runtime monitoring.
Which projects qualify for the new free Secure Registry community tier?
The free tier covers public repositories using GitHub-hosted runners with Harden-Runner. The initial release supports JavaScript package managers including npm, pnpm and Bun, with partial Yarn coverage. Private repositories and self-hosted runners require the enterprise tier.
What operating decisions accompany a package cooldown?
Teams need to decide when to wait, choose an older version or approve a cooldown exemption. Cached dependencies and registry availability also affect coverage and build behavior. Known compromised-package blocking is separate from cooldown exemptions.
How does the financing relate to protection for AI agents?
StepSecurity plans to use the Series A to expand engineering, security research and its commercial organization. Protection for agent sandboxes is among the stated development priorities, alongside its existing developer-machine, repository, registry and CI/CD products.
Where the Money Moved
The intelligence briefing of the innovation economy. Funding, M&A, debt and fund closes, read as market signal rather than deal announcements.
Subscribe to Where the Money Moved