Security posture
Security starts at the local-first boundary.
What Ledgerful reads, writes, and transmits — and what stays on your machine.
Executive summary
The short version for procurement reviewers.
Ledgerful produces technical evidence only; it is not legal advice and does not guarantee regulatory compliance.
| Is source uploaded by default? | No. Analysis runs on your machine. |
|---|---|
| Where does analysis run? | Your machine. Local daemon at 127.0.0.1:52001. |
| Where are keys stored? | Locally. ~/.ledgerful/keys/ (Ed25519). |
| Is evidence signed? | Yes. Every ledger entry is Ed25519-signed. |
| Is telemetry required? | No. Opt-in only, disabled by default. |
| Hosted control plane? | Planned. Not built. |
Procurement facts
What a security reviewer needs to know.
- Security contact
- security@ledgerful.dev (active, monitored)
- Disclosure policy
- Responsible disclosure with safe-harbor. See disclosure section.
- Release verification
- SHA-256 checksums, cosign keyless signing, SLSA build provenance. See release verification.
- SBOM availability
- CycloneDX SBOM published with every release.
- Signing mechanism
- Ed25519 for ledger entries; cosign for release artifacts.
- Data-handling statement
- No source uploads by default. Telemetry is opt-in only.
- Last updated
- July 19, 2026
- Public ledger
- Browser-verifiable signed change ledger at /ledger.
Public ledger
Ledgerful publishes its own development change ledger as a redacted, signed, browser-verifiable bundle. Legacy v1 entries can be Ed25519-verified offline in the browser; v2 provenance rows honesty-fence offline re-verify when redacted fields are required (use local ledgerful verify --signatures).
View the ledger at /ledger, or read the docs at /docs/public-ledger.
What this proves: for v1 sample rows, each entry's Ed25519 signature over the published basis; for v2, signature presence plus the honesty fence (full provenance re-verify needs unredacted local CLI).
What this does not prove: chain continuity, signer identity without an out-of-band key pin, or full v2 free-text provenance when fields are redacted from the public bundle.
Policy as code
Gate merges on declared named rules — offline evaluation, not a compliance certificate.
ledgerful policy check evaluates a flat policy (.ledgerful/policy.toml) against PR/diff/ledger state and exits nonzero on violation. Built-in rules cover signed entries, pending transactions, bound verification, high-risk changes without ADR coverage, and risk thresholds. There is no expression-language DSL.
Honest limit: policy check evaluates the declared rules over the presented ledger and risk inputs. It is not a compliance verdict, certification, or proof that a change is safe. Chain continuity strengthens the presented ledger; it is still not a substitute for your org's change-management process.
Base-branch policy: In CI the enforced policy is the base branch's (or a trusted --policy path), not your PR's. Edits to .ledgerful/policy.toml in a PR branch do not change the gate until they are merged and reviewed on the base branch.
CI role: the engine only evaluates and exits. Posting PR comments or check-runs is the Action wrapper's job, not the engine. See the policy check docs for rules, permissions, and a CI workflow example.
Full security architecture
Data flow, token model, signing, release verification, supply chain, telemetry, threat model, and subprocessors — the complete technical treatment.
Responsible disclosure
security@ledgerful.dev is active. The disclosure channel is verified and active.
Channel status: The security@ledgerful.dev mailbox is provisioned and the engine repository is public with a SECURITY.md policy. GitHub private vulnerability reporting is available on the public repository. No PGP key is published yet; reports are accepted via email or GitHub's private vulnerability reporting.
Forward note: Do not send vulnerability details to a public issue. Check this page for the current verified channel status.
Source repository: The canonical repository is publicly accessible at github.com/Ryan-AI-Studios/Ledgerful. Anonymous HTTPS, GitHub API, and raw-file access are all confirmed. Source-install commands are actionable. Canonical URL: github.com/Ryan-AI-Studios/Ledgerful (opens in new tab). General (non-security) bugs may be reported via GitHub Issues on the public repository.
License
The source terms are PolyForm Noncommercial License 1.0.0 plus the small-entity exception. The license is in force.
The Ledgerful source repository is licensed under PolyForm Noncommercial License 1.0.0 with the Ledgerful Small-Entity Commercial Exception v1.0. The source repository LICENSE file (opens in new tab) and the Small-Entity Commercial Exception reflect the in-force terms. Ledgerful, LLC is formed (FL, effective 2026-07-01); individual→LLC IP assignment is executed; the Small-Entity Commercial Exception is counsel-reviewed; FL + USPTO trademark searches are clear. Introductory Commercial License pricing for broader Internal Business Use is published on Editions; Hosted and Enterprise remain Pricing not announced. Any later change must update the reviewed truth baseline before it reaches public copy. (This website’s own repository is proprietary and separately licensed — all rights reserved, no license granted.)