Hello,
We are currently conducting university research involving code validation that requires an auditable execution environment. We are utilizing the managed Node REPL interface to perform ECMAScript Module (ESM) syntax checks and limited static testing.
Currently, this environment does not expose process.version, process.versions.node, or corresponding V8 version details to user code, nor does public request metadata contain an exact Node host version field.
We would appreciate clarification on the following points:
- Node.js & V8 Version Access: Is there an officially supported, read-only interface to retrieve the exact Node.js version and associated V8 version running the current REPL session?
- Host Build & Deployment Identification: Can a verifiable host build or deployment identifier be provided, along with verification that it corresponds directly to the execution instance running the syntax checks and tests?
- Session Consistency & Lifecycle: Could syntax checking and code execution within the same session migrate across different instances, and under what conditions do related identifiers expire or invalidate?
- Documentation & Roadmap: If this information is not currently exposed to users, are there officially supported attestation mechanisms, product documentation, or upcoming roadmap plans to support this capability?
To be clear, we do not seek to obtain this information through sandbox escapes, child processes, system commands, environment modifications, or undocumented APIs, nor do we require elevated execution privileges. Our sole objective is to accurately document the execution environment and provenance of evidence to ensure our research results can be audited and reproduced.
Thank you.
Hello,
We are currently conducting university research involving code validation that requires an auditable execution environment. We are utilizing the managed Node REPL interface to perform ECMAScript Module (ESM) syntax checks and limited static testing.
Currently, this environment does not expose
process.version,process.versions.node, or corresponding V8 version details to user code, nor does public request metadata contain an exact Node host version field.We would appreciate clarification on the following points:
To be clear, we do not seek to obtain this information through sandbox escapes, child processes, system commands, environment modifications, or undocumented APIs, nor do we require elevated execution privileges. Our sole objective is to accurately document the execution environment and provenance of evidence to ensure our research results can be audited and reproduced.
Thank you.