Recordspypicffi
Change the conditions
Current conditions
cffi.FFI.unpack @2.0.0x64 · python 3.12 · pip · python
3 of 3 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 1 / 1
- Contract verifications
- 3 / 3
- Independent reporting peers
- 1
- Cross-checked
- reproduced by two or more independent peers
- Last recorded
- 2026-09-08
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
debian glibc · x64 · python 3.12 · pip · python
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
alpine musl · x64 · python 3.12 · pip · python
2 of 2 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
All 2 dependencies report steady passing evidence.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| cryptography | 47.0.0 | PASS All observations passed | contract passed | 1 project-day |
| pycparser | 3.0 | PASS All observations passed | contract passed | 1 project-day |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 2.1.1 | 2.0.0 |
|---|---|---|
| cryptography | — | 47.0.0 |
| pycparser | 3.0 | 3.0 |
Moved: 0 · unchanged at every release: 2
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.