
Upstream software project
etcd
highly-available key value store -- client
About etcd
highly-available key value store -- client
This project links 6 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.
These are catalog observations, not a guarantee of installation, compatibility, or upstream support.
Project pictures and package coverage
Project identity
- Project
- etcd
- Publisher
- Not authoritatively mapped
- Native package records
- 6
- Operating systems
- debian-12, debian-13
- License expression
- Not reported
- Metadata completeness
- 95/100 (not a software quality rating)
- Homepage
- Visit upstream site
- Source repository
- Not reported
Source-reported description
The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.
Packages by operating system
Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.
Debian 12 (Bookworm)
- etcd-client3.4.23-4+b4
Debian 12 (Bookworm) / net / source etcd
highly-available key value store -- client
amd64arm64bookworm - etcd-server3.4.23-4+b4
Debian 12 (Bookworm) / net / source etcd
highly-available key value store -- daemon
amd64arm64bookworm - golang-etcd-server-dev3.4.23-4
Debian 12 (Bookworm) / golang / source etcd
highly-available key value store -- source
allbookworm
Debian 13 (Trixie)
- etcd-client3.5.16-4
Debian 13 (Trixie) / net / source etcd
highly-available key value store -- client
amd64arm64trixie - etcd-server3.5.16-4
Debian 13 (Trixie) / net / source etcd
highly-available key value store -- daemon
amd64arm64trixie - golang-etcd-server-dev3.5.16-4
Debian 13 (Trixie) / golang / source etcd
highly-available key value store -- source
alltrixie
Project resources and further reading
Mapping provenance
Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.
No field-level source record is published yet.