votechain-machine implements hardened runtime and operations code for voting workflows.
It is a research and operational prototype and is not guaranteed to meet any jurisdictional election certification framework.
| Version | Supported |
|---|---|
main branch |
Yes |
| Older commits | No |
If you discover a security issue, report it privately. Do not open a public issue.
-
Email security@absurdityindex.org with:
- A clear description of the issue
- Steps to reproduce or a PoC
- Affected component (machine service, relay, ingest, ledger, observer, scripts, docs)
- Severity estimate and impact
-
We will acknowledge within 72 hours.
-
We will coordinate triage and remediation before public disclosure.
- Key management failures (storage, signing, rotation, registry trust)
- Tampering or replay in cast, close, ingest, or relay flows
- Service auth and role/authorization bypasses
- Secret leakage (tokens, DB credentials, chain keys)
- Data integrity failures in audit chains and outbox relays
- Missing or weak threat-model assumptions in consensus-like flows
- Issues limited to local non-networked demo environments with no real trust guarantees
- Non-security UX complaints in demo-only scripts
- Dependabot/update noise in CI pipelines unless it changes security posture
- Cosmetic issues not affecting integrity or trust boundaries
- Performance tuning in non-production demo loads unless it impacts safety
We aim to provide a remediation plan within 90 days. Where protocol changes are required, we will include rationale in release notes and advisory notes.
Security reporters are credited in release notes and advisories when they opt in.