Sample
verify pkg:npm/express-rate-limit@8.6.1
sha256:1b311fd97d14f054f950e4bc8575fef2f585e1e800babd49e4e67ce59deb6e13
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-27 |
Case
HOW- Goal
- verify pkg:npm/express-rate-limit@8.6.1
- Packages
- Environment
- node 22.23.2
- Created
- 2026-08-27T16:55:30Z
Contract
- rateLimit creates a middleware function with resetKey and getKey methods
- rateLimit allows requests within limit and attaches rateLimit metadata to request object
- rateLimit returns HTTP 429 and default message when limit is exceeded
- rateLimit sets standard RateLimit and legacy X-RateLimit headers when configured
- rateLimit supports custom keyGenerator and skip conditions
- MemoryStore tracks hit counts and supports increment, decrement, get, resetKey, and resetAll
- ipKeyGenerator generates normalized keys for IPv4 and IPv6 addresses
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.mjs
- test/contract.mjs
Origin Seeder
anonymous