space-data-module-sdk 0.1.0 → 0.2.0

package/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding any notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2024 Digital Arsenal, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,50 +1,75 @@
 # Space Data Module SDK
 
-A unified SDK for building, validating, signing, and deploying **WebAssembly plugin modules** that run anywhere on the [Space Data Network](https://digitalarsenal.github.io/space-data-network/) — from [OrbPro](https://orbpro.ai) desktops to SDN peer nodes, ground stations, and browsers.
+`space-data-module-sdk` defines the canonical module artifact for the Space Data
+stack: WebAssembly code, an embedded FlatBuffer manifest, a stable capability
+vocabulary, a single-file bundle format, and the signing and transport records
+used to move modules between hosts.
 
-The space domain has a fragmentation problem: every platform ships its own plugin format, its own manifest schema, its own packaging conventions. A propagator written for one system can't run on another without a rewrite. This SDK solves that by defining a **single canonical module format** — a WebAssembly binary with an embedded [FlatBuffers](https://digitalarsenal.github.io/flatbuffers/) manifest — that every runtime in the ecosystem understands.
+This repository is the source of truth for module-level concerns:
 
-Modules declare **typed streaming ports** that accept data conforming to [spacedatastandards.org](https://spacedatastandards.org) schemas (OMM, CAT, EPM, CDM, and 40+ others). A propagator that consumes OMM messages and emits state vectors works identically whether it's running inside OrbPro's 3D scene, processing data on an SDN relay node, or executing at the edge on a ground station.
+- `PluginManifest.fbs` and manifest codecs
+- embedded manifest exports inside `.wasm` modules
+- standards-aware compliance and capability validation
+- module compilation and protection
+- the `sds.bundle` single-file custom section
+- deployment authorization and encrypted transport envelopes
+- the first canonical module hostcall/import ABI surface
 
 <p align="center">
-  <img src="docs/architecture.svg" alt="Architecture overview" width="820" />
+  <img src="docs/architecture.svg" alt="Module architecture overview" width="820" />
 </p>
 
-## How It Works
-
-The SDK handles the full module lifecycle — from source code to a signed, encrypted, deployment-ready package:
-
-<p align="center">
-  <img src="docs/module-lifecycle.svg" alt="Module lifecycle" width="820" />
-</p>
-
-1. **Author** a JSON manifest declaring your module's identity, methods, typed I/O ports, host capabilities, and the [spacedatastandards.org](https://spacedatastandards.org) schemas it consumes and produces.
-2. **Compile** your C/C++ source (via Emscripten) into a `.wasm` binary with the manifest automatically embedded as a FlatBuffers blob that runtimes can read at load time.
-3. **Validate** the manifest and artifact against compliance rules — correct port declarations, canonical capability IDs, required WASM ABI exports (`plugin_get_manifest_flatbuffer`, `plugin_get_manifest_flatbuffer_size`), and schema resolution against the standards catalog.
-4. **Sign** the package with an HD-wallet-derived secp256k1 key, producing a deployment authorization that binds the manifest hash, WASM hash, target, and granted capabilities.
-5. **Protect** the signed package by encrypting it for a specific recipient using X25519 key agreement + AES-256-GCM, so modules can be transported securely across the network.
-
-## Manifest & Typed Ports
-
-Every module carries a manifest that declares **what data it can process**. Methods expose typed input and output ports, and each port declares the FlatBuffer schemas it accepts — referencing standards by schema name and file identifier:
-
-<p align="center">
-  <img src="docs/manifest-structure.svg" alt="Manifest structure" width="820" />
-</p>
-
-This means runtimes can **automatically wire modules together** — connecting a propagator's `CAT` output to a conjunction screener's `CAT` input — without any glue code. The type system ensures only compatible modules get connected.
-
-## Ecosystem
-
-This SDK is one piece of the Space Data Network stack:
-
-| Project | Role |
-|---|---|
-| [Space Data Network](https://digitalarsenal.github.io/space-data-network/) | Peer-to-peer network for space data exchange |
-| [spacedatastandards.org](https://spacedatastandards.org) | 40+ canonical FlatBuffer schemas for space operations data (OMM, EPM, CAT, CDM, etc.) |
-| [FlatBuffers schemas](https://digitalarsenal.github.io/flatbuffers/) | Binary serialization layer used across the entire network |
-| [OrbPro](https://orbpro.ai) | Space domain awareness platform — one of the runtimes that hosts these modules |
-| [hd-wallet-wasm](https://github.com/nicktj-dev/hd-wallet-wasm) | HD wallet primitives for module signing and identity |
+## Artifact Model
+
+A module built with this SDK is a `.wasm` artifact with:
+
+- an embedded `PluginManifest.fbs`
+- exported manifest accessors:
+  - `plugin_get_manifest_flatbuffer`
+  - `plugin_get_manifest_flatbuffer_size`
+- optional `sds.bundle` custom-section payloads for:
+  - manifest bytes
+  - deployment authorization
+  - detached signatures
+  - encrypted transport envelopes
+  - auxiliary FlatBuffer or raw payloads
+
+The module contract stays the same whether the artifact is loaded directly,
+wrapped in a deployment envelope, or shipped as one bundled `.wasm` file.
+
+## Runtime Portability
+
+The module format is language-neutral. A host can load modules from this SDK
+anywhere it can:
+
+- instantiate WebAssembly
+- read FlatBuffers
+- honor the module capability and host ABI contract
+
+That target set matches the WebAssembly and FlatBuffers runtime families already
+used in the companion `flatbuffers/wasm` work:
+
+- browser
+- Node.js
+- C#
+- Go
+- Java
+- Kotlin
+- Python
+- Rust
+- Swift
+
+This repo currently includes:
+
+- the JavaScript reference implementation for manifest, compliance, auth,
+  transport, bundle handling, and compilation
+- deterministic `sds.bundle` conformance vectors under
+  [`examples/single-file-bundle/vectors`](./examples/single-file-bundle/vectors)
+- non-JS bundle reference clients in
+  [`examples/single-file-bundle/go`](./examples/single-file-bundle/go) and
+  [`examples/single-file-bundle/python`](./examples/single-file-bundle/python)
+- a reference Node host and sync `sdn_host` bridge for the first hostcall
+  surface
 
 ## Install
 
@@ -56,84 +81,150 @@ npm install space-data-module-sdk
 
 ```js
 import {
-  encodeManifest, decodeManifest,   // FlatBuffers manifest codec
-  checkCompliance,                   // validate against standards
-  signManifest, verifyManifest,      // HD wallet auth
-  encryptPayload, decryptPayload,    // X25519 + AES-256-GCM transport
-  compileModule,                     // source-to-wasm compilation
+  compileModuleFromSource,
+  createSingleFileBundle,
+  encodePluginManifest,
+  parseSingleFileBundle,
+  validateManifestWithStandards,
 } from "space-data-module-sdk";
-```
 
-### Subpath Exports
+const manifestBytes = encodePluginManifest(manifest);
+const validation = await validateManifestWithStandards(manifest);
+if (!validation.ok) {
+  throw new Error("Manifest validation failed.");
+}
+
+const compilation = await compileModuleFromSource({
+  manifest,
+  sourceCode,
+  language: "c",
+});
 
-Each subsystem is available as a standalone import:
+const bundle = await createSingleFileBundle({
+  wasmBytes: compilation.wasmBytes,
+  manifest,
+});
+
+const parsed = await parseSingleFileBundle(bundle.wasmBytes);
+```
+
+Each subsystem is also available as a subpath export:
 
 ```js
-import { encodeManifest } from "space-data-module-sdk/manifest";
-import { checkCompliance } from "space-data-module-sdk/compliance";
-import { signManifest }    from "space-data-module-sdk/auth";
-import { encryptPayload }  from "space-data-module-sdk/transport";
-import { compileModule }   from "space-data-module-sdk/compiler";
-import { resolveStandard } from "space-data-module-sdk/standards";
+import { encodePluginManifest } from "space-data-module-sdk/manifest";
+import { validateManifestWithStandards } from "space-data-module-sdk/compliance";
+import { createDeploymentAuthorization } from "space-data-module-sdk/auth";
+import { encryptJsonForRecipient } from "space-data-module-sdk/transport";
+import { compileModuleFromSource } from "space-data-module-sdk/compiler";
+import { createSingleFileBundle } from "space-data-module-sdk/bundle";
 ```
 
-## CLI
+## Single-File Bundles
+
+`sds.bundle` keeps module delivery to one file without changing WebAssembly
+loadability. The SDK appends a standard custom section, not raw trailer bytes,
+so the bundled artifact still compiles as a normal `.wasm` module.
 
-Every SDK operation is also available from the command line:
+The reference path lives in
+[`examples/single-file-bundle`](./examples/single-file-bundle):
+
+- [`demo.mjs`](./examples/single-file-bundle/demo.mjs) builds and parses a
+  bundled module
+- [`generate-vectors.mjs`](./examples/single-file-bundle/generate-vectors.mjs)
+  regenerates the checked-in conformance vectors
+- the `go` and `python` directories show non-JS readers against the same
+  bundle contract
+
+## Host ABI
+
+This repo also defines the module-facing capability vocabulary and the first
+synchronous hostcall bridge under the import module `sdn_host`.
+
+The current sync import surface is:
+
+- `call_json(operation_ptr, operation_len, payload_ptr, payload_len) -> i32`
+- `response_len() -> i32`
+- `read_response(dst_ptr, dst_len) -> i32`
+- `last_status_code() -> i32`
+- `clear_response() -> i32`
+
+Use `createNodeHost(...)` and `createNodeHostSyncHostcallBridge(...)` to run
+that contract against the reference Node host while keeping the ABI shape
+portable for non-JS hosts.
+
+## Host Capabilities
+
+Modules request capabilities by stable ID. The current recommended vocabulary
+includes:
+
+`clock` `random` `logging` `timers` `schedule_cron` `http` `tls` `websocket`
+`mqtt` `tcp` `udp` `network` `filesystem` `pipe` `pubsub` `protocol_handle`
+`protocol_dial` `database` `storage_adapter` `storage_query` `storage_write`
+`context_read` `context_write` `process_exec` `crypto_hash` `crypto_sign`
+`crypto_verify` `crypto_encrypt` `crypto_decrypt` `crypto_key_agreement`
+`crypto_kdf` `wallet_sign` `ipfs` `scene_access` `entity_access`
+`render_hooks`
+
+Manifests can also declare coarse runtime targets for planning and compliance:
+
+`node` `browser` `wasi` `server` `desktop` `edge`
+
+## Environment Notes
+
+| Surface | Node.js | Browser |
+|---|---|---|
+| `manifest` | Yes | Yes |
+| `auth` | Yes | Yes |
+| `transport` | Yes | Yes |
+| `bundle` | Yes | Yes |
+| `compliance` | Yes | No |
+| `compiler` | Yes | No |
+| `standards` | Yes | No |
+
+## CLI
 
 ```bash
-# Validate a manifest + wasm pair against compliance rules
+# Validate a manifest + wasm pair
 npx space-data-module check --manifest ./manifest.json --wasm ./dist/module.wasm
 
-# Compile C/C++ source to a wasm module with embedded manifest
+# Compile C/C++ source and embed the manifest
 npx space-data-module compile --manifest ./manifest.json --source ./src/module.c --out ./dist/module.wasm
 
-# Sign and encrypt a module package for transport
+# Sign and encrypt a deployment payload
 npx space-data-module protect --manifest ./manifest.json --wasm ./dist/module.wasm --json
+
+# Emit a single-file bundled wasm
+npx space-data-module protect --manifest ./manifest.json --wasm ./dist/module.wasm --single-file-bundle --out ./dist/module.bundle.wasm
 ```
 
 ## Module Lab
 
-An interactive browser tool for compiling, validating, and packaging modules — useful for exploring the manifest format and testing modules without touching the CLI.
+The repo also includes a local browser lab for compiling, validating, and
+packaging modules:
 
 ```bash
 npm run start:lab
-# http://localhost:4318
 ```
 
-## Plugin Families
-
-Modules declare a `pluginFamily` that tells runtimes what role they serve:
-
-| Family | Purpose |
-|---|---|
-| `sensor` | Ingest raw data feeds (radar, optical, RF) |
-| `propagator` | Orbit propagation and state prediction |
-| `renderer` | 3D visualization and scene rendering |
-| `analysis` | Data processing, filtering, aggregation |
-| `data_source` | External data connectors |
-| `comms` | Communications link modeling |
-| `shader` | GPU shader programs |
-| `sdf` | Signed distance field geometry |
-| `infrastructure` | Network and platform services |
-| `flow` | Multi-module data flow orchestration |
-| `bridge` | Cross-runtime adapters |
-
-## Host Capabilities
+Then open `http://localhost:4318`.
 
-Modules request host capabilities by name. The runtime grants or denies them at load time based on the deployment authorization:
+## Related Projects
 
-`clock` `random` `timers` `http` `network` `filesystem` `pipe` `pubsub` `protocol_handle` `protocol_dial` `database` `storage_adapter` `storage_query` `storage_write` `wallet_sign` `ipfs` `scene_access` `render_hooks`
+- [`spacedatastandards.org`](https://spacedatastandards.org)
+- [`@digitalarsenal/sdn-flow`](https://github.com/DigitalArsenal/sdn-flow)
+- [`hd-wallet-wasm`](https://github.com/nicktj-dev/hd-wallet-wasm)
 
 ## Development
 
 ```bash
 npm install
 npm test
+npm run check:compliance
 ```
 
-Requires Node.js >= 20. Compilation requires [Emscripten](https://emscripten.org/) (`emcc`/`em++`) on `PATH`.
+Node.js `>=20` is required. Native compilation paths use Emscripten
+(`emcc` / `em++`) when available.
 
 ## License
 
-See [LICENSE](LICENSE).
+[MIT](./LICENSE)

package/bin/space-data-module.js

@@ -24,6 +24,11 @@ async function main(argv) {
       return runCompile(rest);
     case "protect":
       return runProtect(rest);
+    case "help":
+    case "--help":
+    case "-h":
+      printUsage();
+      return 0;
     default:
       printUsage();
       return command ? 1 : 0;
@@ -33,6 +38,7 @@ async function main(argv) {
 function parseArgs(argv) {
   const options = {
     json: false,
+    singleFileBundle: false,
     repoRoot: process.cwd(),
     manifestPath: null,
     wasmPath: null,
@@ -49,6 +55,9 @@ function parseArgs(argv) {
       case "--json":
         options.json = true;
         break;
+      case "--single-file-bundle":
+        options.singleFileBundle = true;
+        break;
       case "--repo-root":
         options.repoRoot = path.resolve(requireValue(argv, ++index, value));
         break;
@@ -95,6 +104,7 @@ function printUsage() {
   space-data-module check --manifest ./manifest.json --wasm ./dist/module.wasm
   space-data-module compile --manifest ./manifest.json --source ./src/module.c --out ./dist/module.wasm
   space-data-module protect --manifest ./manifest.json --wasm ./dist/module.wasm --json
+  space-data-module protect --manifest ./manifest.json --wasm ./dist/module.wasm --single-file-bundle --out ./dist/module.bundle.wasm
 `);
 }
 
@@ -201,6 +211,9 @@ async function runProtect(argv) {
   if (!options.manifestPath || !options.wasmPath) {
     throw new Error("protect requires --manifest and --wasm.");
   }
+  if (options.outputPath && options.singleFileBundle !== true) {
+    throw new Error("protect only supports --out together with --single-file-bundle.");
+  }
   const manifest = await loadManifestFromFile(options.manifestPath);
   const wasmBytes = new Uint8Array(await readFile(options.wasmPath));
   const result = await protectModuleArtifact({
@@ -208,7 +221,11 @@ async function runProtect(argv) {
     wasmBytes,
     recipientPublicKeyHex: options.recipientPublicKeyHex,
     mnemonic: options.mnemonic,
+    singleFileBundle: options.singleFileBundle,
   });
+  if (options.singleFileBundle && options.outputPath && result.bundledWasmBytes) {
+    await writeFile(options.outputPath, result.bundledWasmBytes);
+  }
   if (options.json) {
     console.log(JSON.stringify(result, null, 2));
   } else {
@@ -216,6 +233,13 @@ async function runProtect(argv) {
     console.log(`signingPublicKeyHex=${result.signingPublicKeyHex}`);
     console.log(`encrypted=${result.encrypted}`);
     console.log(`wasmBase64Length=${bytesToBase64(wasmBytes).length}`);
+    if (result.bundledWasmBytes) {
+      console.log(`singleFileBundle=true`);
+      console.log(`bundledWasmBytes=${result.bundledWasmBytes.length}`);
+    }
+    if (options.outputPath) {
+      console.log(`outputPath=${options.outputPath}`);
+    }
   }
   return 0;
 }

package/package.json

@@ -1,8 +1,9 @@
 {
   "name": "space-data-module-sdk",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Module SDK for building, validating, signing, and deploying WebAssembly modules on the Space Data Network.",
   "type": "module",
+  "types": "./src/index.d.ts",
   "bin": {
     "space-data-module": "./bin/space-data-module.js"
   },
@@ -13,6 +14,7 @@
     "./auth": "./src/auth/index.js",
     "./transport": "./src/transport/index.js",
     "./compiler": "./src/compiler/index.js",
+    "./bundle": "./src/bundle/index.js",
     "./standards": "./src/standards/index.js",
     "./schemas/*": "./schemas/*"
   },
@@ -24,11 +26,14 @@
   "scripts": {
     "test": "node --test",
     "start:lab": "node ./lab/server.js",
-    "check:compliance": "node ./bin/space-data-module.js check --repo-root ."
+    "check:compliance": "node ./bin/space-data-module.js check --repo-root .",
+    "generate:vectors": "node ./examples/single-file-bundle/generate-vectors.mjs",
+    "prepublishOnly": "npm test && npm run check:compliance"
   },
   "dependencies": {
+    "sdn-emception": "1.0.0",
     "flatbuffers": "^25.9.23",
-    "hd-wallet-wasm": "^1.5.4",
+    "hd-wallet-wasm": "1.6.0",
     "spacedatastandards.org": "23.3.3-0.3.4"
   },
   "devDependencies": {