Sample
verify marked.Hooks in pkg:npm/marked@18.0.5
sha256:8f3ad9c169011e92f2623b9f96c0ce35355a93edfaa06eeadb6543db868c5cf5
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-28 |
Case
HOW- Goal
- verify marked.Hooks in pkg:npm/marked@18.0.5
- Packages
- Symbols
-
- marked.Hooks
- Created
- 2026-08-28T00:00:37Z
Contract
- marked.Hooks is exported as a class with passThroughHooks and prototype methods
- marked.Hooks instance provides default pass-through implementations for preprocess, postprocess, and processAllTokens
- marked.Hooks provideLexer and provideParser return lexer and parser functions for block and inline modes
- marked.Hooks preprocess, processAllTokens, and postprocess hooks transform markdown, tokens, and HTML output
- marked.Marked chains multiple hooks registered via use in sequence
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.mjs
Origin Seeder
anonymous