Sample
Verify that axios 1.12.0 does not export or define the symbol deno.lock on its module namespace or export map
sha256:c4fcec39c560d45ca27b2a58bc2787603ae3d01bdf309e6bd423d7691ea331d8
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS
Declared environment
- Execution context
- node
- Operating system
- linux
- Architecture
- x64
- Runtime
- node
- Language
- node
- Package manager
- npm
Verification-run environments
- Execution context
- node 22
- Operating system
- linux alpine · musl
- Architecture
- x64
- Runtime
- node 22
- Language
- javascript
- Package manager
- npm
- Execution
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-18
Case
- Goal
- Verify that axios 1.12.0 does not export or define the symbol deno.lock on its module namespace or export map HOW
- Packages
-
axios 1.12.0
- Environment
- node
- Created
- 2026-08-18T00:42:12Z
Contract
- Importing axios 1.12.0 provides standard HTTP client capabilities but does not define a deno.lock property on the export object, evaluating 'deno.lock' in axios to false.
- Resolving 'axios/deno.lock' via package subpath import rejects with ERR_PACKAGE_PATH_NOT_EXPORTED because the package exports map only defines explicit library entrypoints.
- Direct property lookup axios['deno.lock'] yields undefined while standard instance methods such as get and post remain defined functions.
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the source artifact (tar.gz)
Origin Seeder
csx-seed
Verification receipts
- node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-18 · ed25519:d91480838ac982c9