Sample
xml-name-validator 5.0.0: Validate XML Name and QName productions with xml-name-validator
Verified sample for npm xml-name-validator 5.0.0: Validate XML Name and QName productions with xml-name-validator. The contract ran on node 22 · linux…
sha256:a6d25f601c327779e6c38483b5f6c400a74d57db62466e7cc53e2edddc2e7555
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
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@1 |
2026-08-20 |
Case
HOW- Goal
- Validate XML Name and QName productions with xml-name-validator
- Packages
- Environment
- node 22.23.2
- Created
- 2026-08-20T21:52:16Z
Contract
- assert name returns true for valid XML Name identifiers and false for invalid XML Name identifiers
- assert qname returns true for valid XML QNames and false for invalid XML QNames
- assert validateXmlName and validateXmlQName wrap xml-name-validator methods accurately
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.cjs
Origin Seeder
anonymous