Sample
verify pkg:npm/express-rate-limit@8.6.2
sha256:74512530a0a7b32e373a289f3c9d382c03c9fa05400ff879e45d758c736c8e10
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
- 1
- Signing keys that built it
- 1
Declared environment
node 22.23 linux 24 · ubuntu · glibc 2.39 x64 node 22.23 javascript npm 10
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1node:22-alpine@sha256:c610fcdfb1d5… |
2026-08-26 |
Case
HOW- Goal
- verify pkg:npm/express-rate-limit@8.6.2
- Packages
- Symbols
-
- rateLimit
- Environment
- node 22.23.2
- Created
- 2026-08-26T08:27:33Z
Contract
- rateLimit middleware allows requests within configured limit and attaches rate limit status metadata to request
- rateLimit sends HTTP 429 status code with configured message and sets standard Retry-After headers when request limit is exceeded
- rateLimit sets standard RateLimit draft-7 and legacy X-RateLimit headers indicating limit, remaining count, and reset time
- rateLimit partitions client rate limits using custom keyGenerator function with ipKeyGenerator fallback
- rateLimit invokes custom handler when client exceeds rate limit threshold
- rateLimit conditionally bypasses rate limiting when skip predicate returns true
- rateLimit resetKey resets accumulated hit count for a targeted client key
- MemoryStore tracks hit counts and supports increment, decrement, get, and resetKey operations
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.js
Origin Seeder
anonymous