Recordscargolibc0.2.190
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| alpine musl | ubuntu glibc | |
|---|---|---|
| libc::_SC_CLK_TCK | 100%2 | 100%2 |
| libc::_SC_PAGESIZE | 100%1 | 100%3 |
| libc::_SC_PAGE_SIZE | 100%1 | 100%3 |
| libc::c_int | 100%1 | 100%5 |
| libc::c_long | 100%1 | 100%4 |
| libc::sysconf | 100%1 | 100%4 |
Showing the environments with the most evidence.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| unknown · Rust · cargo · linux glibc
Observations: PROJECT_COMPILE 4✓ · PROJECT_PROCESS 22✓ · PROJECT_TEST 2✓ — Usage: USED 2✓
|
LOW | 28 +2 | 0 | 100% | 1 | 2026-10-16 |
| rust 1 · Rust · cargo · linux musl · docker
Observations: PROJECT_LOAD 3✓ · PROJECT_TEST 3✓ — Usage: USED 4✓ — Verified: CONTRACT 12✓
|
LOW | 6 +4 | 12 | 100% | 1 · 1✓ | 2026-10-16 |
Symbols
- getpid 1 1 of 1 runs passed
- libc::_SC_CLK_TCK 1 1 of 1 runs passed
- libc::_SC_PAGESIZE 1 1 of 1 runs passed
- libc::_SC_PAGE_SIZE 1 1 of 1 runs passed
- libc::c_int 1 1 of 1 runs passed
- libc::c_long 1 1 of 1 runs passed
- libc::getpid 1 1 of 1 runs passed
- libc::getppid 1 1 of 1 runs passed
- libc::pid_t 1 1 of 1 runs passed
- libc::sysconf 1 1 of 1 runs passed
- sysconf 1
Published samples
- libc 0.2.190 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-10-15