Sample
verify constrainedMemory in pkg:npm/bare-os@3.9.3
sha256:1048c2ce83c9c564a6cc83ca94b0dc5a7b2b14ed2992971a6d6effcaa98a7268
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
linux 24 · ubuntu · glibc 2.39 x64 npm
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 constrainedMemory in pkg:npm/bare-os@3.9.3
- Packages
- Symbols
-
- constrainedMemory
- Created
- 2026-08-27T06:13:06Z
Contract
- constrainedMemory is exported as a function on bare-os
- constrainedMemory returns a non-negative integer representing memory limit in bytes or 0 when unconstrained
- getConstrainedMemory returns the exact numeric value from os.constrainedMemory
- isMemoryConstrained accurately indicates whether memory constraints are active
- getEffectiveMemoryLimit falls back to totalmem when unconstrained and uses constrained limit when active
- constrainedMemory executes deterministically and without side effects across multiple invocations
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous