Sample
has-symbols 1.1.0: hasNativeSymbols, hasSymbols
Verified sample for npm has-symbols 1.1.0: hasNativeSymbols, hasSymbols. The contract ran on node 22 · linux alpine/x64 · docker and passed…
sha256:335a6888833cc5b1c69510a9b3f0ad1b28ab0a11f7ad15641e47e61ca669612b
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
windows 11 x64 npm
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/has-symbols@1.1.0
- Packages
- Symbols
-
- hasNativeSymbols
- hasSymbols
- Created
- 2026-08-18T17:57:24Z
Contract
- hasNativeSymbols() returns true in modern JavaScript runtimes with native Symbol support
- hasSymbols() from has-symbols/shams.js returns true when Symbol and Object.getOwnPropertySymbols are supported
- native symbols created with Symbol() produce distinct symbol primitives non-enumerable in Object.keys
- Object.getOwnPropertySymbols retrieves symbol properties assigned to objects
- wrapper functions checkNativeSymbols and checkSymbolsOrShams match direct library calls
Files
- PROMPT.md
- csx.json
- index.mjs
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous