Sample
sinatra 4.2.1: Show that Sinatra does not automatically delete uploaded tempfile after request
Verified sample for gem sinatra 4.2.1: Show that Sinatra does not automatically delete uploaded tempfile after request. The contract ran on ruby 3 · linux…
sha256:642785541c948ed29ed0bfef28fd354b3908b3e42d5b60ff220ab91e5a7a7f29
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.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
ruby linux x64 ruby ruby bundler
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| ruby 3 · linux debian/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-17 |
| ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-18 |
Case
HOW- Goal
- Show that Sinatra does not automatically delete uploaded tempfile after request
- Packages
- Symbols
-
- Sinatra::Base#post
- Rack::Test::UploadedFile
- Environment
- ruby
- Created
- 2026-08-17T02:47:53Z
Contract
- A multipart upload sent with an allowed localhost Host reaches the Sinatra route, and the received tempfile still exists after the request returns.
Files
- Gemfile
- Gemfile.lock
- csx.json
- test/contract.rb