Sample
verify ScopeManager and analyze in eslint-scope
sha256:df1e530fb8fe83a1ab67d39dfcdf32c40f235d338dd110d638af56383753f7ab
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 ScopeManager and analyze in eslint-scope
- Packages
- Symbols
-
- ScopeManager
- analyze
- Created
- 2026-08-27T23:11:11Z
Contract
- analyze generates a ScopeManager with global and module scopes from ESTree AST
- ScopeManager.acquire retrieves the Scope associated with an AST node
- ScopeManager.getDeclaredVariables returns variables declared by an AST node
- Scope tracks variable references and distinguishes read and write operations
- GlobalScope.through records unresolved references to undeclared variables across nested scopes
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous