space-data-module-sdk 0.8.13 → 0.8.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -779,6 +779,8 @@ inspect the parsed `REC`, `PNM`, and `ENC` records produced by the real
779
779
 
780
780
  - [`spacedatastandards.org`](https://spacedatastandards.org)
781
781
  - [`hd-wallet-wasm`](https://github.com/nicktj-dev/hd-wallet-wasm)
782
+ - [`flatsql`](https://github.com/DigitalArsenal/flatsql) — the FlatBuffer-native
783
+ query engine behind `createFlatSqlRuntimeStore()`
782
784
 
783
785
  ## Development
784
786
 
@@ -817,4 +819,19 @@ helpers for serialized command execution and virtual filesystem access.
817
819
 
818
820
  ## License
819
821
 
820
- [MIT](./LICENSE)
822
+ [Apache-2.0](./LICENSE)
823
+
824
+ ### Dependency licenses
825
+
826
+ The SDK's own license (above) does not change, but one runtime dependency is
827
+ no longer permissive: as of `flatsql` **2.0.0** the FlatSQL engine is licensed
828
+ under the [PolyForm Noncommercial License
829
+ 1.0.0](https://polyformproject.org/licenses/noncommercial/1.0.0/) — source-available
830
+ and free for any noncommercial purpose, with commercial use requiring a separate
831
+ license from DigitalArsenal.io, Inc.
832
+ ([tj@digitalarsenal.io](mailto:tj@digitalarsenal.io)). Installing this package
833
+ installs `flatsql`, so a commercial deployment of anything built on the SDK's
834
+ FlatSQL-backed runtime-host storage needs that license. Every `flatsql` release
835
+ before 2.0.0 has been withdrawn from npm, so `^2.0.0` is the only resolvable
836
+ floor — see [`docs/flatsql-host-contract.md`](./docs/flatsql-host-contract.md)
837
+ for why the major bump changes no API.
@@ -1,4 +1,9 @@
1
- # The FlatSQL host contract (why the floor moved to ^1.4.4)
1
+ # The FlatSQL host contract (why the floor moved to ^1.4.4, then to ^2.0.0)
2
+
3
+ The current floor is **`^2.0.0`**. The 1.x history below is what made the
4
+ contract, and it still describes the contract 2.0.0 ships — see
5
+ [The 2.0.0 floor is a licence change, not a port](#the-200-floor-is-a-licence-change-not-a-port)
6
+ at the end for why the major bump costs nothing here.
2
7
 
3
8
  ## The defect the bump repairs
4
9
 
@@ -93,3 +98,31 @@ consumer would actually load. At 1.4.4 it reports `in-surface (WASI + declared
93
98
  capabilities: 7)`, `satisfied` in the real-browser lane and
94
99
  `runner-cannot-supply-declared-capability` under the bare WasmEdge CLI, naming
95
100
  `env.flatsql_io_open` as the single blocker.
101
+
102
+ ## The 2.0.0 floor is a licence change, not a port
103
+
104
+ `flatsql` 2.0.0 is 1.4.5's code republished under the [PolyForm Noncommercial
105
+ License 1.0.0](https://polyformproject.org/licenses/noncommercial/1.0.0/).
106
+ The major is semver signalling the licence, not an API break. Measured on the
107
+ two published tarballs, every file is byte-identical except three:
108
+
109
+ ```
110
+ LICENSE Apache-2.0 -> PolyForm Noncommercial 1.0.0
111
+ package.json "version" and "license" only
112
+ README.md licence + contact section
113
+ ```
114
+
115
+ The host contract above therefore carries over unchanged. On
116
+ `wasm/flatsql-wasi.wasm`, 2.0.0 imports the same **13** — the seven
117
+ `flatsql_io_*` on `env` plus six WASI preview1 — and exports the same **102**
118
+ as 1.4.4, so the parity gate classifies the 2.0.0 engine exactly as it
119
+ classified 1.4.4.
120
+
121
+ Two consequences for anyone reading this floor:
122
+
123
+ - **Every pre-2.0.0 `flatsql` is withdrawn from npm.** A pin below `^2.0.0`
124
+ resolves to nothing. There is no supported lower floor.
125
+ - **Commercial use of the engine needs a licence** from DigitalArsenal.io, Inc.
126
+ ([tj@digitalarsenal.io](mailto:tj@digitalarsenal.io)). The SDK stays MIT and
127
+ consumes flatsql through its JS API only, but installing the SDK installs the
128
+ engine, so the obligation reaches the SDK's consumers.
package/package.json CHANGED
@@ -1,6 +1,7 @@
1
1
  {
2
2
  "name": "space-data-module-sdk",
3
- "version": "0.8.13",
3
+ "version": "0.8.14",
4
+ "license": "Apache-2.0",
4
5
  "description": "Module SDK for building, validating, signing, and deploying WebAssembly modules on the Space Data Network.",
5
6
  "type": "module",
6
7
  "types": "./src/index.d.ts",
@@ -109,7 +110,7 @@
109
110
  "dependencies": {
110
111
  "flatbuffers": "^25.9.23",
111
112
  "flatc-wasm": "^26.1.32",
112
- "flatsql": "^1.4.4",
113
+ "flatsql": "^2.0.0",
113
114
  "hd-wallet-wasm": "2.0.28",
114
115
  "sdn-emception": "1.0.0",
115
116
  "spacedatastandards.org": "https://github.com/DigitalArsenal/spacedatastandards.org/archive/06deda5079204a46bd97a7ce6ac2868e991c6b8f.tar.gz"
@@ -121,4 +122,4 @@
121
122
  "engines": {
122
123
  "node": ">=20.0.0"
123
124
  }
124
- }
125
+ }
@@ -13,7 +13,7 @@
13
13
  "test": "node --test tests/*.test.mjs"
14
14
  },
15
15
  "dependencies": {
16
- "space-data-module-sdk": "^0.8.12"
16
+ "space-data-module-sdk": "^0.8.14"
17
17
  },
18
18
  "private": true
19
19
  }