Recordspypimarkupsafe3.0.3markupsafe.soft_str
OS × runtime at a glance
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.
Published samples
- markupsafe 3.0.3: Pin MarkupSafe __html__ protocol evaluation discrepancies between format() and escape(), format specifier rejections, % helper type errors, and mutation auto-escaping 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. HOWMarkupEscapeFormatterescapesoft_strpython MIT-0 · 2026-08-17
Compatibility matrix
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.10 · Python · pip · windows
Observations: PROJECT_PROCESS 2✓
|
LOW | 2 | 0 | 100% | 1 | 2026-08-17 |
| python 3.12 · Python · pip · linux glibc
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-31 |
snapshot · 2026-09-15
Failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 3.0.3 os=linux · runtime=python@3.12 sha256:53f88c6b1d5f…Traceback (most recent call last): · File <str>, line 4, in <module> · from src.renderer import ( · ModuleNotFoundError: No module named <str>python3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 3.0.3 os=linux · runtime=python@3.12 sha256:177ec3ab8c3e…File <str>, line 80 · raw = <str> · ^^^^^ · SyntaxError: invalid syntaxpython3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate