Trust Center
Evidence for security reviews
Security policy, supply-chain records, code assurance, provenance and compliance notes for Aster, generated from the repository on every build.
Drawn by AsterIn review. Most records here, and the scripts and files they cite, are on a review branch and not in the main source tree yet. Each record and file reference says which.
Everything you need to evaluate Aster's security, supply chain and compliance posture in one place, with each claim linked to evidence you can check.
- Aster is a CPU rendering and UI toolkit made by Barnyard Greens LLC.
- The SDK and examples are MIT licensed; the runtime is free to use under the Aster Runtime EULA.
- Its core runs inside your process, has no telemetry, and opens no network connections in its default build.
- The runtime source code is private; each claim below names a way to check it against the binary or the release records.
- Security contactme@barnyak.com
- PolicySecurity policy
01
Data and privacy
02
Security and vulnerability handling
03
Supply chain and releases
Supply chain: SBOM, licences, advisories, vetting, reproducibility
Everything here is produced by scripts under tools/trust/ that run inside one pinned docker image. One command runs it all: tools/trust/check.sh (the future CI job). It writes tools/trust/out/summary.json; a dated…
Read the recordReleases: signing, provenance and verification
Status: the tooling in tools/trust/ is implemented and tested with throw-away keys. The real release key does not exist yet; the key ceremony below is a later step and is written down so that it can be reviewed first.…
Read the record04
Code assurance
Unsafe code policy and inventory
Status: as of 2026-11-11. Numbers below are generated by tools/unsafe/inventory.py (a real Rust lexer, not grep: comments, strings, raw strings and lifetimes are handled) and committed as…
Read the recordFuzzing
Status: as of 2026-11-11. The harnesses and seed corpora are committed and compile; the long fuzzing campaigns have not been run yet (see "Hours run" below). Nothing on this page claims coverage or findings that were not…
Read the record05
Source, provenance and support
Verifying a release
The Aster Runtime source code is private, so verification works on the release files.
Read the recordProvenance and AI use
How Aster's code is written and reviewed, where the earlier Aster code comes from, and what we can and cannot say about copyright in AI-assisted code.
Read the recordSupport and versioning policy
How Aster is versioned, how long each release is supported, how security fixes are delivered, and what to expect before 1.0.
Read the record06
Compliance and questionnaires
EU Cyber Resilience Act readiness
What the EU Cyber Resilience Act (Regulation (EU) 2024/2847) means for Aster as software maintained by a company, with a dated timeline and our current state.
Read the recordSSDF mapping and draft attestation
A draft mapping of NIST SP 800-218 (SSDF v1.1) practices to what Aster does today, with gaps stated, and a draft of the CISA secure software development attestation. DRAFT. Not submitted. Not signed.
Read the recordExport control self-assessment
Status: UNDER REVIEW (2026-11-15). The earlier version assumed published open-source software. The runtime source is private, so the published-source exemption (reasoning 1) is not relied on. Counsel to redo this…
Read the recordSecurity questionnaire answers
Pre-written answers for the common sections of vendor security questionnaires (SIG Lite, CAIQ, HECVAT style) for Aster, a data-free, on-premises, in-process library (SDK and examples under the MIT licence, runtime under…
Read the record07
Licences and records
The Aster SDK and examples are released under the MIT licence; the runtime ships under the Aster Runtime EULA. The runtime source is private; the records here let you check a release without it: signed checksums, build provenance, a software bill of materials and a licence inventory.
Signed releases, SBOMs and VEX statements stay in place alongside these; see release verification and supply chain.
08
Requests
These records are public. For anything specific to your deployment, write to me@barnyak.com.
SBOM and VEX
The component list for a specific build, plus exploitability statements when a component has a known vulnerability.
Build verification
Hashes and provenance for a shipped binary.
Security questionnaire
Pre-filled answers for common questionnaires, with evidence references; buyer-specific forms on request.
Free support
Support is free for now; there are no paid plans. The support policy takes effect at 1.0.
09
Phase 0 status
Phase 0 is the set of zero-cost trust items. Status as of 2026-11-11, not yet released.
| # | Item | Status | Where / what is left |
|---|---|---|---|
| 1 | Checkable "no data" claim | Done | No data: what Aster does and does not do, tools/trust/no-io-check.sh, I/O behind off-by-default features net-sync and persist. Left: run it in CI once CI exists |
| 2 | Vulnerability process | In progress | Policy written (Security policy, Vulnerability handling policy). Left: create the security@ mailbox, CNA arrangement, named contacts, ENISA registration |
| 3 | SBOM and license inventory | In progress | Supply chain: SBOM, licences, advisories, vetting, reproducibility |
| 4 | Signed releases, provenance, reproducible builds | In progress | Releases: signing, provenance and verification |
| 5 | Dependency CI | In progress | Supply chain: SBOM, licences, advisories, vetting, reproducibility |
| 6 | The unsafe story (inventory, rule, Miri, fuzzing) | In progress | Unsafe code policy and inventory, Fuzzing |
| 7 | SSDF self-attestation draft | Done (draft) | SSDF mapping and draft attestation. Not submitted; gaps listed |
| 8 | Provenance and AI-use policy | Done | Provenance and AI use, CONTRIBUTING.md. Left: confirm the authorship record of the earlier code, the copyright holder line and the EULA text, counsel review, DCO or CLA decision |
| 9 | Export note | Under review | Export control self-assessment: under review: the earlier published-source basis no longer applies. Left: counsel |
| 10 | CRA readiness note | Done (draft) | EU Cyber Resilience Act readiness. Left: counsel review, technical file |
Check a claim yourself
Each claim names the file in the repository that proves it.