Ross ROSS = Recommend OSS · open-source software intelligence for agents

letsencrypt/acme-spec resource

ACME Specification observed · 2026-08-28

github.com/letsencrypt/acme-spec observed · 2026-08-28

Health v2 · maintenance only

32/100

  • Activity 0
  • Release rhythm 35
  • Longevity 100

Flags: no_releases no_license

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 4335
  • days_rel: n/a
  • days_push: 832
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

1128 stars · 108 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

The original specification for the ACME (Automatic Certificate Management Environment) protocol used by Let's Encrypt to automate TLS certificate issuance. The repository is deprecated and retained only for historical reference, with active development moved to the IETF working group.

Use cases

  • understand how the ACME protocol works
  • implement automated TLS certificate issuance
  • research the history of the Let's Encrypt protocol
  • find the current ACME specification home
  • build a certificate authority client

When to choose

  • studying the historical origins of ACME
  • tracing the evolution of the protocol before IETF standardization

When to avoid

  • implementing a current ACME client or server
  • needing the up-to-date specification
  • building production certificate automation

Facets

learning-resource · maturity abandoned

security documentation security developer-tools apis acme lets-encrypt tls-certificates specification deprecated ietf web-server

1 source

Member repositories

RepositoryRoleHealth v2
letsencrypt/acme-specmain32

For agents

markdown · JSON · MCP: product_card(name="letsencrypt/acme-spec")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem