# veorq/cryptocoding

Guidelines for low-level cryptography software

Repository: https://github.com/veorq/cryptocoding
Canonical: https://ross.abutalabs.com/products/cryptocoding
License Family: other
Last push: 2023-06-11T17:36:41+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 2717, "days_push": 1179, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1218, forks 93 (observed 2026-08-28T04:04:01.575076+00:00)

## What it is
A curated set of coding rules and best practices for implementing low-level cryptographic software, originally from the cryptocoding.net 'Crypto coding standard'. It covers topics like constant-time comparison, avoiding secret-dependent branches and table lookups, strong randomness, and cleaning secret data from memory.

## Use cases
- write constant-time comparisons for secrets
- avoid side-channel vulnerabilities in crypto code
- learn secure C coding practices for cryptography
- review cryptographic implementation for timing attacks
- find best practices for zeroing secret memory
- guidelines for using strong randomness in code

## When to choose
- you are implementing or reviewing low-level cryptographic primitives in C
- you want a checklist of side-channel-resistant coding rules
- you are teaching or learning secure crypto implementation practices

## When to avoid
- you need a working cryptography library rather than guidelines
- you write only high-level application code with no secret-handling logic
- you need language-specific or framework-specific security standards

## Facets
- artifact type: learning-resource
- maturity: maintenance
- function: security, cryptography, documentation, developer-tools
- domain: security, developer-tools, documentation, programming-languages
- platform: cpp, c, cross-platform
- tags: secure-coding, constant-time, side-channel-attacks, cryptography-guidelines, best-practices, memory-zeroization

## Member repositories
- veorq/cryptocoding (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:01.575076+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:17:05.766986+00:00, confidence not recorded.
  - readme: https://github.com/veorq/cryptocoding (fetched 2026-08-28T04:04:01.575076+00:00, sha 710b17429bc9)
- Data as of 2026-08-30T08:39:29.467469+00:00.