Recordspypicryptography41.0.7
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
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 |
|---|---|---|---|---|---|---|
| python 3.12 · Python · pip · linux glibc · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 6✓
|
LOW | 4 +2 | 6 | 100% | 1 · 1✓ | 2026-09-17 |
| python 3.12 · Python · uv · linux glibc
Observations: PROJECT_PROCESS 2✓
|
LOW | 2 | 0 | 100% | 1 | 2026-09-13 |
| python 3.12 · Python · pip · linux glibc
Observations: PROJECT_PROCESS 3✓ — Verified: UNKNOWN 0✓ 1✕
|
LOW | 3 | 1 | 75% | 1 | 2026-09-13 |
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 41.0.7 os=linux · runtime=python@3.12 cryptography.exceptions.InvalidTag sha256:d4423b6bd381…Traceback (most recent call last): · File <str>, line 114, in <module> · main() · File <str>, line 106, in mainpython3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13Diagnostic re-verification candidate
Symbols
- algorithms.AES 1 1 of 1 runs passed
- cryptography.exceptions.AlreadyFinalized
- cryptography.exceptions.AlreadyUpdated
- cryptography.hazmat.primitives.ciphers.Cipher 1 0 of 1 runs passed
- modes.GCM 1
- cryptography.exceptions.InvalidTag 1 1 of 2 runs passed
- cryptography.exceptions.UnsupportedAlgorithm
- cryptography.hazmat.primitives.ciphers.algorithms 0 of 1 runs passed
- authenticate_additional_data 1 1 of 1 runs passed
- finalize 1
- cryptography.hazmat.primitives.hashes
- cryptography.hazmat.primitives.hmac
- cryptography.hazmat.primitives.ciphers.modes 0 of 1 runs passed
- cryptography.hazmat.primitives.padding