Skip to main content
Any Framework

Supply chain security CLI for .NET and Node.js — vulnerability scanning, SBOM generation, and policy enforcement

Published
Sep 12, 2026
2mo ago
Total Downloads
1.3K
1,321

Install

dotnet add package Rorix.Cli --version 0.1.0

No framework information available.

README

Rorix

Rorix is a .NET and Node.js supply-chain security platform for vulnerability scanning, SBOM generation, license policy, trusted packages, pentesting, and gated code analysis. It scans NuGet and npm dependency manifests while keeping the trusted registry and source-analysis betas .NET-specific. This repository contains the Next.js application, worker services, CLIs, and CI integrations.

Local development

Requirements: Node.js 24, pnpm 10, PostgreSQL 16, .NET 9, Go 1.24, and Docker for the HTTP E2E suite.

cp .env.example .env.local
pnpm install --frozen-lockfile
pnpm run db:migrations:check
pnpm test
pnpm run lint
pnpm run build

Start the web app with pnpm dev. Start the full local stack with docker compose up --build; the web app is exposed at http://localhost:3001 and internal services remain on the Compose network.

Release verification

pnpm audit --prod
pnpm --dir services/code-analysis audit --prod
pnpm --dir services/code-analysis test
go test ./...
dotnet build dotnet-tool/Rorix.Cli/Rorix.Cli.csproj
dotnet pack dotnet-tool/Rorix.Cli/Rorix.Cli.csproj --no-build
pnpm run release:cli:check
pnpm test:e2e

The public site is intentionally labeled as a public preview until every external gate in docs/launch-readiness.md is complete. Never publish a release merely because the application build passes.

Production

Production requires the variables documented in .env.example, the full migration set in drizzle/, and separately deployed pentest and Code Analysis services. Webhook signing and PostgreSQL-backed rate limiting fail closed when their production secrets or database are unavailable.

See docs/launch-readiness.md for the release procedure, required infrastructure, marketplace publication, legal, monitoring, and rollback gates. CLI publishing uses the GitHub OIDC procedure in docs/runbooks/cli-release.md; no long-lived NuGet API key is permitted.

Adoption Assessment

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.