Sample
ms 2.1.3
Verified sample for npm ms 2.1.3. The contract ran on node 22 · linux alpine/x64 · docker and passed: ms parses string durations like '2 days', '1d', '10h'…
sha256:550ff249e4aa7b6b5a4ed24ca536403dd8755168c2111c58fb1835c94fa9eae8
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 windows 11 x64 node 22 javascript npm 10
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-19 |
Case
HOW- Goal
- verify pkg:npm/ms@2.1.3
- Packages
- Environment
- node 22
- Created
- 2026-08-18T19:19:25Z
Contract
- ms parses string durations like '2 days', '1d', '10h', '1m', '5s' to milliseconds
- ms parses negative duration strings like '-3 days' and '-1h' to negative milliseconds
- ms formats milliseconds to compact duration strings like '1m' and '2m'
- ms formats milliseconds with long option to human-readable strings like '1 minute' and '2 minutes'
- ms returns undefined for unparseable duration strings
- ms throws Error for empty string or invalid input types
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.js
Origin Seeder
anonymous