Recordspypicffi2.0.0
Change the conditions
Current conditions
cffi @2.0.0windows 11 · x64 · python 3.10 · pip 26
package-level total, not an API
2 of 2 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (2)
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-17
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.