Recordspypityping-inspection0.4.4
Change the conditions
Current conditions
typing-inspection @0.4.4windows 11 · x64 · python 3.10 · pip 26
package-level total, not an API
0 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 (1)
- Project observations
- 0 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 2
- Last recorded
- 2026-08-14
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.4.4
windows · python@3.10
2 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| typing-extensions | 4.16.0 | PASS All observations passed | contract passed | 4 project-days |
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 | 0.4.4 | 0.4.2 |
|---|---|---|
| typing-extensions | 4.16.0 | 4.16.0 |
Moved: 0 · unchanged at every release: 1
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.
Recent failure clusters
-
observed PROJECT_PROCESS Evidence gap ×2 0.4.4 os=windows · runtime=python@3.10Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-14 · Last seen: 2026-08-14Diagnostic re-verification candidate