Files
git.stella-ops.org/docs
StellaOps Bot e923880694
Some checks failed
AOC Guard CI / aoc-guard (push) Has been cancelled
AOC Guard CI / aoc-verify (push) Has been cancelled
Concelier Attestation Tests / attestation-tests (push) Has been cancelled
Docs CI / lint-and-preview (push) Has been cancelled
Export Center CI / export-ci (push) Has been cancelled
Mirror Thin Bundle Sign & Verify / mirror-sign (push) Has been cancelled
feat: Add DigestUpsertRequest and LockEntity models
- Introduced DigestUpsertRequest for handling digest upsert requests with properties like ChannelId, Recipient, DigestKey, Events, and CollectUntil.
- Created LockEntity to represent a lightweight distributed lock entry with properties such as Id, TenantId, Resource, Owner, ExpiresAt, and CreatedAt.

feat: Implement ILockRepository interface and LockRepository class

- Defined ILockRepository interface with methods for acquiring and releasing locks.
- Implemented LockRepository class with methods to try acquiring a lock and releasing it, using SQL for upsert operations.

feat: Add SurfaceManifestPointer record for manifest pointers

- Introduced SurfaceManifestPointer to represent a minimal pointer to a Surface.FS manifest associated with an image digest.

feat: Create PolicySimulationInputLock and related validation logic

- Added PolicySimulationInputLock record to describe policy simulation inputs and expected digests.
- Implemented validation logic for policy simulation inputs, including checks for digest drift and shadow mode requirements.

test: Add unit tests for ReplayVerificationService and ReplayVerifier

- Created ReplayVerificationServiceTests to validate the behavior of the ReplayVerificationService under various scenarios.
- Developed ReplayVerifierTests to ensure the correctness of the ReplayVerifier logic.

test: Implement PolicySimulationInputLockValidatorTests

- Added tests for PolicySimulationInputLockValidator to verify the validation logic against expected inputs and conditions.

chore: Add cosign key example and signing scripts

- Included a placeholder cosign key example for development purposes.
- Added a script for signing Signals artifacts using cosign with support for both v2 and v3.

chore: Create script for uploading evidence to the evidence locker

- Developed a script to upload evidence to the evidence locker, ensuring required environment variables are set.
2025-12-03 07:51:50 +02:00
..
2025-11-25 08:01:23 +02:00
up
2025-11-27 21:09:47 +02:00
up
2025-11-27 08:52:59 +02:00
up
2025-11-24 07:52:25 +02:00
up
2025-11-24 07:52:25 +02:00
up
2025-11-25 22:09:44 +02:00
up
2025-11-26 07:47:08 +02:00
up
2025-11-24 07:52:25 +02:00
2025-11-25 08:01:23 +02:00
2025-11-21 06:56:36 +00:00
up
2025-11-25 22:09:44 +02:00
up
2025-11-26 20:23:28 +02:00
2025-11-23 23:38:25 +02:00
up
2025-12-01 21:16:22 +02:00
up
2025-11-27 07:46:56 +02:00
up
2025-11-27 15:16:31 +02:00
up
2025-11-27 21:10:06 +02:00
up
2025-11-30 21:01:00 +02:00
up
2025-11-25 22:09:44 +02:00
up
2025-11-25 22:09:44 +02:00
up
2025-11-27 21:10:06 +02:00
up
2025-11-27 21:10:06 +02:00
up
2025-11-26 20:23:28 +02:00
2025-12-02 18:38:32 +02:00
up
2025-11-26 20:23:28 +02:00
2025-11-25 08:01:23 +02:00
2025-11-25 08:01:23 +02:00
up
2025-11-29 01:35:49 +02:00
up
2025-11-27 21:10:06 +02:00
2025-11-21 06:56:36 +00:00
up
2025-11-25 22:09:44 +02:00
up
2025-11-26 20:23:28 +02:00
up
2025-11-27 07:46:56 +02:00
2025-11-21 06:56:36 +00:00
2025-11-23 23:38:25 +02:00
2025-11-23 23:38:25 +02:00
2025-11-23 23:38:25 +02:00
up
2025-11-28 09:41:08 +02:00
up
2025-11-30 21:01:00 +02:00

StellaOps

StellaOps is the sovereign, SBOMfirst security platform that proves every container decision with deterministic scans, explainable policy verdicts, and offlineready provenance.

  • Sovereign by design bring your own trust roots, vulnerability advisory sources, VEX sources, regional crypto, and Offline Update Kits that never phone home.
  • Deterministic + replayable every scan can be reproduced bitforbit with DSSE + OpenVEX evidence.
  • Actionable signal lattice logic ranks exploitability, and the policy engine lets you tailor VEX handling, muting, and expiration rules for your environment.

Proof points: SBOM dependency and vulnerability dependency cartographing work, deterministic replay manifests, lattice policy UI with OpenVEX, and postquantum trust packs ready for regulated sectors.

Choose Your Path

If you want to… Open this Read time
Understand the promise and pain we solve overview.md 2min
Run a first scan and see the CLI quickstart.md 5min
Browse key capabilities at a glance key-features.md 3min
Check architecture, road to production, or evaluate fit See “Dig deeper” below 30min curated set

Explore the Essentials

  1. Value in context Overview compresses the “Why” + “What” stories and shows how StellaOps stands apart.
  2. Try it fast Quickstart walks through fetching the signed bundles, configuring .env, and verifying the first scan.
  3. Feature confidence Key Features gives five capability cards covering Delta SBOM, VEX-first policy, Sovereign crypto, Deterministic replay, and Transparent quotas.
  4. Up-next checkpoints Evaluation checklist helps teams plan Day-0 to Day-30 adoption milestones.
  5. Be dev-ready Developer Quickstart (29-Nov-2025 advisory) walks through the core repos, determinism tests, attestations, and starter issues for a mid-level .NET engineer.

Key capabilities that define StellaOps

Capability What ships Why it matters
Deterministic ΔSBOM & replay bundles Layer-aware cache + replay manifests keep scans reproducible even months later. Auditors can re-run any verdict with identical inputs, proving integrity without SaaS dependencies.
Pristine advisory mirrors OSV, GHSA, NVD, CNVD, CNNVD, ENISA, JVN, BDU, etc. are mirrored as immutable, per-source snapshots—never merged. Policy (via scanner.* / SCANNER__*) can trust, down-rank, or ignore sources without rewriting upstream data.
Lattice VEX engine OpenVEX, waivers, mitigations, and configs flow through deterministic lattice logic. Every block/allow decision is explainable, replayable, and environment-specific.
Context fabric Static reachability now, optional runtime/eBPF probes at GA so build + runtime signals share one verdict. Prioritisation spans first-party code, base images, and live telemetry.
Transparency log + trust credits Cosign/DSSE bundles push to a Rekor-compatible log; the trust-credit ledger records who accepted a risk. Compliance teams get provenance plus accountable ownership trails.
Sovereign crypto profiles Swap in FIPS, eIDAS, GOST, SM, or PQ-ready providers without code changes. Meets regional crypto rules while keeping attestations verifiable.
Offline-first operations Offline Kit packages the pristine feeds, plug-ins, and configs; import CLI verifies everything locally. Air-gapped clouds get the same security posture as connected sites.
Enterprise readiness Transparent quotas, LDAP/AD SSO, restart-time plug-in SDK, generous free tier. Large teams keep their workflows without surrendering control to SaaS platforms.

Where StellaOps differs from incumbents

Vendor Where they stop StellaOps difference
Trivy / Syft SBOM generation as a CLI add-on; policy left to other products. SBOM + VEX are the system of record with deterministic replay and signed evidence.
Snyk Container Static reachability bounded to first-party code. Lattice links code, base images, cluster policies, and optional runtime probes so the entire stack shares one score.
JFrog Xray Contextual scoring lives behind a closed service. Policies, DSSE bundles, and transparency logs are open, auditable, and portable.
Docker Scout Provenance remains inside Dockers ecosystem. Any OCI provenance is ingested, signed with your crypto profile, and replayed offline.
Wiz / runtime sensors Runtime telemetry is separate from build-time SBOM/VEX evidence. Optional runtime probes feed the same deterministic lattice so build- and run-time context stay consistent.

Dig Deeper (curated reading)

Need more? The full documentation tree ADRs, permodule operations, schemas, developer references stays untouched under the existing directories (modules/, api/, dev/, ops/), ready when you are.

Configuration note: Feature exposure stays governed by StellaOps.Scanner.WebService (scanner.* / SCANNER__*) settings. See modules/scanner/architecture.md and modules/scanner/design/surface-env.md for the authoritative schema; the docs remain pristine while configuration decides what surfaces for each deployment.

© 2025 StellaOps contributors AGPL3.0orlater