CodeSampleX

Sample

verify availableMemory in pkg:npm/bare-os@3.9.3

sha256:5e8654f649f978a87ecf4ffda8389e1e5efd924084b8252a05dfcb04f8b799c6

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 availableMemory in pkg:npm/bare-os@3.9.3
Packages
Symbols
  • availableMemory
Created
2026-08-27T06:10:45Z

Contract

  1. bare-os package manifest exports root module with availableMemory API and index.d.ts type declarations
  2. index.d.ts declares availableMemory returning a number representing available system memory in bytes
  3. index.js exports availableMemory function delegating to native binding availableMemory call
  4. native binding.c implements bare_os_available_memory using uv_get_available_memory and registers availableMemory export
  5. bare-os availableMemory returns a non-negative number when executed with the addon runtime binding

Files

  • PROMPT.md
  • csx.json
  • package-lock.json
  • package.json
  • spec.json
  • test/contract.mjs

Download the source artifact (tar.gz)

Origin Seeder

anonymous