signetry

Seal every agent's PR with proof — earned authority in a signed receipt.

The umbrella overview for the Signetry platform — a change-control plane for coding agents.

signetry.github.io · Architecture · Integrations · Compatibility · Install

---

Coding agents can now change your repository. Signetry is the layer that decides how much authority a given change has earned — and proves it. Any executor (Claude Code, Codex, Cursor, Copilot, a human) may propose a change; only Signetry may admit authority and seal a signed receipt.

This repository is the front door: the single overview humans and agents open first. It owns no governance code — that lives in signetry-core, the one kernel every surface depends on. This repo is the map of the city.

Mental model

Layer	What it is
signetry-umbrella (this repo)	The overview: architecture, integration catalog, compatibility matrix, release train, install map.
signetry-core	The kernel — the only place governance logic lives (policy, guard, admit, dual verifier, plan binding, gates, passport, receipt, extension admission, CLI, MCP server). Also ships the layered SAST detection engine (signetry scan, 7 languages, cross-file taint, SARIF) and governed fix fusion (signetry scan --fix → admission → signed receipt).
Each integration repo	A district — its own release, CI, and Marketplace/plugin review; depends on pinned signetry-core.
Admission Decision Pack	The same passport stamp used in every district.

flowchart TB
  Org[GitHub_Org_Signetry]
  Umbrella[signetry-umbrella_overview]
  Core[signetry-core]
  Hosted[signetry_hosted]
  Action[signetry-action]
  Plugins[signetry-plugins]

  Org --> Umbrella
  Org --> Core
  Org --> Hosted
  Org --> Action
  Org --> Plugins

  Umbrella -.->|catalog_compatibility_release_train| Core
  Core --> Hosted
  Core --> Action
  Core --> Plugins

Loading

The one guarantee

Every admit run — from the CLI, the GitHub Action, the API, an MCP tool, or the hosted console — returns one Admission Decision Pack: a verdict (admit/cap/block), the earned authority level (L0 observe / L1 analyze / L2 branch-PR), machine-readable reasons, the contract / trust-boundary / checks / verifier reports, the exact proposed diff, and an Ed25519-signed receipt an auditor can verify offline. auto_merge is always false — a human merges.

See ARCHITECTURE.md for the full design (the source of truth).

Detect & fix, then govern

signetry-core also finds vulnerabilities and can govern the fix. signetry scan is a deterministic, offline SAST engine across 7 languages (Python, JavaScript, Go, Java, Ruby, PHP, C#) with cross-file taint and SARIF output; signetry scan --fix turns a finding into a bounded remediation an agent drafts under the admission pipeline, sealed in a signed receipt — branch-only, never merged, bring-your-own-key.

On a public 52-case, 7-language head-to-head (signetry-eval), signetry-core reaches 100% recall at 0 false positives — matching/leading a top LLM scanner (Claude Opus 4.8 at 90%) while staying deterministic, offline, and free. Detection is table stakes; the governance above is what the scanners don't attempt.

Contributing — Apache-2.0, PRs welcome

Signetry is open core. This umbrella repo and the whole integration surface are Apache-2.0: read it, run it, fork it, ship it commercially — no permission needed, no strings. The engine (signetry-core) is source-available under BUSL-1.1 and converts to Apache-2.0 on 2030-08-31. Full map: LICENSING.md.

Contributions are accepted under a Contributor License Agreement — kept deliberately, because code moves across the open-core line: an adapter contributed here may later be promoted into the engine, and engine code is released outward as its licence converts. The CLA is what lets that happen without re-asking every contributor. You keep every right the licence gives everyone else, and you are credited in CONTRIBUTORS.md, the Git history, and release notes.

Contributing is easy and welcome:

• 🌱 Good first issues (tracking board): Signetry/signetry#10 — well-scoped tasks with exact files + acceptance criteria.
• 💬 Questions / ideas: Discussions
• 📝 How to contribute + sign the CLA: CONTRIBUTING.md here, plus each child repo's own CONTRIBUTING.md and CLA.md (e.g. signetry-core). The best first PR is adding a detection test case in signetry-eval.

The strongest contribution targets are signetry-core (the engine), signetry-eval (the benchmark), and signetry-reviewer — each has tests + CI to validate your PR.

Start here

• New to Signetry? → ARCHITECTURE.md
• Want to install it in a day? → INSTALL.md
• Which repo do I want? → INTEGRATIONS.md
• Which versions work together? → COMPATIBILITY.md
• How do releases flow? → RELEASE.md
• Want to contribute? → good first issues · Discussions
• Announcing / sharing Signetry? → LAUNCH.md
• What is licensed how? → LICENSING.md

Contributors

Gratefully credited for contributions accepted under the CLA, which keeps code free to move across the open-core line. Each grid links to that repo's contributor graph and updates automatically.

core — the kernel	action — Marketplace
reviewer	eval — the benchmark
plugins	signetry — this repo

_{Want your seal here? Open a PR, sign the CLA, and you're credited. Start with a good first issue.}

License

Apache-2.0. Use it, fork it, ship it commercially — no strings.

This repository is part of Signetry's open-core model: the integration surface is Apache-2.0 so anyone can add an agent, an editor, or a CI adapter, while the engine (Signetry/core) is source-available under BUSL-1.1 and converts to Apache-2.0 on 2030-08-31.

Contributions are accepted under the CLA — it lets us move a well-built adapter into the engine later without asking every contributor for permission again.