This policy covers the Telarch libraries from Perseus Computing LLC: Harpe, Kibisis and Argus.
| Package | Version | Supported |
|---|---|---|
harpe |
>= 0.1.0-alpha.2 |
✅ |
kibisis |
>= 0.1.0-alpha.2 |
✅ |
argus-ledger |
>= 0.1.0-alpha.2 |
✅ |
Please do not report security vulnerabilities through public GitHub issues or discussions.
Instead, please email:
contact@perseuscomputing.com
with the subject line: [SECURITY VULNERABILITY] <Component Name>. No PGP key is published.
- Acknowledgement: Within 48 hours of initial receipt.
- Triage & Assessment: Within 5 business days, detailing validity and planned mitigation.
- Remediation & Patch: Target release within 14 calendar days for verified high and critical vulnerabilities.
- Coordinated Disclosure: We request a 90-day embargo period from the date of initial report to allow users to upgrade before public disclosure.
Telarch libraries are designed for local and disconnected use on developer, server, or edge hardware:
- No Network Surface: Telarch libraries do not open network sockets, bind HTTP endpoints, or transmit telemetry.
- Local Isolation: Memory bounds and cryptographic verifications assume the local operating system process boundary is intact.
- Argus Tamper Evidence: Argus detects and locates changes to past events in an append-only linear hash chain. On its own, a truncated chain, or one recomputed by someone who can write the log, still verifies. Sign events with a key, and keep the latest sequence number and hash somewhere the writer cannot change, to detect those too.
- Kibisis Encryption: The Python package seals each entry with AES-256-GCM. With
sqlcipher3installed, SQLCipher also encrypts the whole database file; without it, categories, keys and metadata are stored in plain text. The Rust crate holds memory in RAM and does not encrypt it.