
Upstream software project
klibc
kernel headers used during the build of klibc
About klibc
kernel headers used during the build of klibc
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
- klibc
- 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)
- klibc-utils2.0.12-1
Debian 12 (Bookworm) / libs / source klibc
small utilities built with klibc for early boot
amd64arm64bookworm - libklibc2.0.12-1
Debian 12 (Bookworm) / libs / source klibc
minimal libc subset for use with initramfs
amd64arm64bookworm - libklibc-dev2.0.12-1
Debian 12 (Bookworm) / libdevel / source klibc
kernel headers used during the build of klibc
amd64arm64bookworm
Debian 13 (Trixie)
- klibc-utils2.0.14-1
Debian 13 (Trixie) / libs / source klibc
small utilities built with klibc for early boot
amd64arm64trixie - libklibc2.0.14-1
Debian 13 (Trixie) / libs / source klibc
minimal libc subset for use with initramfs
amd64arm64trixie - libklibc-dev2.0.14-1
Debian 13 (Trixie) / libdevel / source klibc
kernel headers used during the build of klibc
amd64arm64trixie
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.