Recordsgemrack-protection4.2.1Sinatra::Base#condition
shared with 5 packages — this evidence cannot say whose API it is
Published samples
- sinatra 4.2.1: Demonstrate how Sinatra's route pass mechanism preserves response status codes, headers, cookies, and params mutations across route conditions and fallback handlers 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. HOWSinatra::Base#passSinatra::Base#conditionSinatra::Base#statusSinatra::Base#headersSinatra::Response#set_cookieSinatra::Base#paramsruby MIT-0 · 2026-08-16
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 |
|---|---|---|---|---|---|---|
| ruby 3 · ruby · bundle · linux glibc · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-18 |
snapshot · 2026-08-30
Failure clusters
No failure clusters observed.