@lossless.org/objectstorage 11.0.0 → 11.1.0

package/readme.md

@@ -69,7 +69,7 @@ described below.
 ### Clustering Features
 
 - 🔗 **Erasure coding** — Reed-Solomon (configurable k data + m parity shards) for storage efficiency and fault tolerance
-- 🚄 **QUIC transport** — multiplexed inter-node communication via `quinn` with zero head-of-line blocking. Encrypted but not authenticated: run it only on a trusted network (see Cluster transport trust).
+- 🚄 **QUIC transport** — multiplexed inter-node communication via `quinn` with zero head-of-line blocking. Mutual TLS with a cluster CA when `cluster.tls` is set; without it, encrypted but not authenticated, for trusted networks only (see Cluster transport trust).
 - 💽 **Multi-drive awareness** — each node manages multiple independent storage paths with health monitoring
 - 🩺 **Cluster health introspection** — query native node, drive, quorum, and healing status for product dashboards
 - 🤝 **Cluster membership** — static seed config + runtime join, heartbeat-based failure detection
@@ -184,8 +184,9 @@ Cluster mode requires the control root and every drive root to exist before
 startup. The process user must own them, no path component may be a symlink,
 and group/world write permission must be disabled.
 
-The cluster transport does not authenticate nodes: run cluster mode only on a
-network where every host that can reach `quicPort` is a cluster node (see
+Without `cluster.tls` the cluster transport does not authenticate nodes: run
+cluster mode only on a network where every host that can reach `quicPort` is a
+cluster node, or set `cluster.tls` on every node (see
 [Cluster transport trust](#cluster-transport-trust)).
 
 ```typescript
@@ -286,7 +287,7 @@ const config: IObjectStorageConfig = {
   },
   cluster: {                 // Optional — omit for standalone mode
     enabled: true,
-    nodeId: 'node-1',        // Auto-generated UUID if omitted
+    nodeId: 'node-1',        // Auto-generated UUID if omitted; required with tls
     quicPort: 4000,          // Default: 4000
     seedNodes: [],           // Addresses of existing cluster members
     erasure: {
@@ -301,6 +302,16 @@ const config: IObjectStorageConfig = {
     heartbeatIntervalMs: 5000,  // Default: 5000
     heartbeatTimeoutMs: 30000,  // Default: 30000
     getDeadlineMs: 21600000,    // Default: 6 h; 60000 (1 min) to 604800000 (7 d)
+    tls: {                      // Optional mutual TLS; set on every node or on none
+      caFile: '/etc/objectstorage/tls/ca.pem',
+      certFile: '/etc/objectstorage/tls/node-1.pem', // its DNS SAN is nodeId
+      keyFile: '/etc/objectstorage/tls/node-1.key',  // mode 0600 or 0400
+    },
+  },
+  dashboard: {               // Optional read-only dashboard; off unless enabled
+    enabled: true,
+    address: '127.0.0.1',    // Default: '127.0.0.1'
+    port: 3001,              // Default: 3001; 0 allocates an ephemeral TCP port; never the S3 port
   },
 };
 
@@ -1011,6 +1022,23 @@ interface IClusterHealth {
   drives?: IClusterDriveHealth[];
   erasure?: IClusterErasureHealth;
   repairs?: IClusterRepairHealth;
+  transport?: IClusterTransportHealth;
+}
+
+interface IClusterTransportHealth {
+  mode: 'mutualTls' | 'unauthenticated';
+  certificate?: { sha256: string; notAfter: number };      // only with mutualTls
+  caCertificates?: { sha256: string; notAfter: number }[]; // file order; only with mutualTls
+}
+
+type TDriveMedia = 'rotational' | 'smr' | 'flash' | 'zoned';
+
+interface IClusterDriveHealth {
+  // index, path, status, capacity, error and erasure set fields, plus:
+  media: {
+    declared?: TDriveMedia;              // not reported yet: drives cannot declare their media
+    detected: TDriveMedia | 'unknown';   // detected once at startup
+  };
 }
 ```
 
@@ -1018,10 +1046,88 @@ interface IClusterHealth {
 - Standalone mode returns `{ enabled: false }`.
 - Peer status is the local node's current view of cluster membership and heartbeats, so it is best-effort and may lag real network state.
 - Drive health is based on live native probe checks on the configured local drive paths. Capacity values are cheap filesystem snapshots.
+- `drives[].media.detected` is the medium the engine detected for each drive once at startup, never per health call. On Linux it follows the drive root's filesystem to the whole disk behind it (`st_dev` through `/sys/dev/block`; a partition counts as its disk) and reads the disk's `queue/zoned` and `queue/rotational`: `zoned` for host-managed or host-aware devices (SMR or ZNS), otherwise `rotational` or `flash`, as the disk's driver sets `queue/rotational`. Virtual and network block devices report the flag their driver or hypervisor sets: QEMU disks show `rotational` unless they are configured with `rotation_rate=1`, and NVMe volumes show `flash`. Declaring a drive's media, which is planned, is what will correct such a reading. It is `unknown`, never a guess, for filesystems without a block device of their own (tmpfs, overlay, network and FUSE filesystems, btrfs subvolumes), for device-mapper, md, loop and other virtual block devices (LVM, dm-crypt and software RAID included), when sysfs gives no usable answer, and on every platform but Linux. Drive-managed SMR reports itself as rotational and cannot be detected (`smr` can only ever be declared). The detected media change no behaviour today.
 - `quorumHealthy` means the local node currently sees majority quorum and enough available placements in every erasure set to satisfy the configured write quorum.
+- `transport.mode` is `mutualTls` when `cluster.tls` is set and `unauthenticated` otherwise. With mutual TLS, `certificate` and `caCertificates` describe the files the engine loaded at startup: the SHA-256 of each DER certificate (lowercase hex) and its `notAfter` in milliseconds since the Unix epoch. The files are read only at startup, so during a certificate or CA rotation these show what each node actually runs.
 - Repair fields expose the background healer's currently available runtime state. They are best-effort and limited to what the engine tracks today, such as whether a scan is active, the last completed run, and the last error.
 - `repairs.shardsChecked`, `shardsHealed` and `failed` count the last completed scan's placement checks, shards written and failures. `repairs.shardsPending` counts the pending shards (see [Self-Healing](#self-healing)) that scan left pending because their drive was out of reach, refused the write, or their object was busy. While a scan runs, `lastRunStartedAt` is the running scan's start and the counts are still the previous scan's; `runHealingScan()` returns one scan's start and counts together.
 
+## Dashboard
+
+Every node can serve a small read-only dashboard for quick visibility: the
+cluster's nodes, drives, erasure layout and quorum, object and byte totals,
+request, error and byte rates, healing state and recent engine events. It is
+off by default:
+
+```typescript
+const storage = await ObjectStorage.createAndStart({
+  // ...
+  dashboard: { enabled: true, address: '10.0.0.5', port: 3001 },
+});
+console.log(storage.dashboardPort); // the bound port; undefined while off
+```
+
+Open `http://<address>:<port>/` in a browser. The page is bundled into the
+package (`ts_web/`, built into `ts/dashboard.bundled.ts`), so nothing is
+fetched from elsewhere, and it updates itself over one TypedSocket connection
+to the same origin.
+
+- **Configuration.** `dashboard.enabled` must be set. `address` defaults to
+  `127.0.0.1` and `port` to `3001`; `port: 0` asks the OS for a port. A port
+  equal to `server.port` is refused at construction. A dashboard that is
+  enabled but cannot bind fails `start()`, and the engine is stopped: it never
+  runs silently without it. The `dashboard` section is not sent to the engine.
+- **What it shows.** Nodes (status and last heartbeat in this node's view,
+  start time); local drives of every node (status, usage, errors,
+  last probe); the erasure layout and quorum; objects and bytes per node and
+  summed; request, error and byte rates per node and summed, with two-minute
+  sparklines kept in the browser; healing per node (last scan, checked,
+  healed, pending shards, failures); and the newest events of each node (peer
+  status changes, drive status changes, healing scan results, engine start).
+  A standalone node shows its totals, rates and events. Rates are derived
+  from counters of the S3 listener; byte counts are taken at the TCP stream
+  and include HTTP headers. Nothing is stored: a reload starts the sparklines
+  again.
+- **Where the data comes from.** One management command, `getClusterSnapshot`
+  (also `ObjectStorage.getClusterSnapshot()`), built by the engine from memory
+  only: the drive states the last heartbeat probe left, the in-memory runtime
+  stats, healing state, S3 listener counters and a ring of the newest 64
+  events. It never probes a drive, syncs, walks a directory or reads the
+  control store. A cluster node asks each online peer for that peer's own
+  snapshot over QUIC (`NodeSnapshot`), in parallel, with one second per peer;
+  a peer that is not online or does not answer in time shows as unavailable in
+  that sample. Any node with the dashboard on therefore shows the whole
+  cluster, and the other nodes need no dashboard of their own.
+- **Cost.** With no dashboard connected there is no timer, no IPC and no QUIC
+  traffic. While at least one is connected, one shared sampler takes a
+  snapshot every two seconds, keeps at most one in flight and skips ticks
+  while one runs, and pushes the same sample (a few KB per node) to every
+  connected dashboard. At most 16 dashboard sockets are admitted at once; the
+  17th is refused with `503`. On the engine side, request and byte counting is
+  a relaxed atomic add per response and per socket read or write. An enabled
+  dashboard with nobody watching runs no timer and sends no traffic; on a
+  three-node cluster against 11.0.0 its CPU cost per request was within 0.4 %,
+  and the engine's memory was unchanged. Its server modules and bundled page
+  add about 50 MiB to the Node.js process of each node once, at start, and
+  that does not grow with time or stored objects. With 16 dashboards open on
+  every node, large uploads ran about 1.5 % slower and the p99 latency was
+  about 5 % higher.
+- **Security.** The dashboard is read-only by construction: its socket
+  registers one read handler and nothing else, so it cannot start a healing
+  scan, change configuration or touch S3 traffic or stored data. It has no
+  authentication: protect it with the bind address and a firewall, for
+  example by binding it to a private interface only. It shows node IDs,
+  addresses, drive paths, counts and event messages, never credentials or
+  object keys.
+- **Versions.** Run every node on the same version, as clusters already
+  require. An engine that predates `NodeSnapshot` cannot decode the request,
+  logs a stream error and closes the stream, and the asking node shows it as
+  unavailable.
+
+`getClusterHealth()` probes every local drive (a write, sync and read of a
+probe file) on each call; poll `getClusterSnapshot()` instead when you need a
+cheap periodic view.
+
 ## Supported S3 Operations
 
 The router fails closed, in standalone and cluster mode alike. A request
@@ -1455,16 +1561,79 @@ ahead of the client.
 ### QUIC Transport
 
 Inter-node communication uses [QUIC](https://en.wikipedia.org/wiki/QUIC) via the `quinn` library:
-- **Encrypted, not authenticated** — each node generates a self-signed certificate at startup and accepts any peer; run it only on a trusted network (see [Cluster transport trust](#cluster-transport-trust))
+- **Mutual TLS or unauthenticated** — with `cluster.tls`, every connection is TLS 1.3 with a CA-signed certificate on both ends; without it, each node generates a self-signed certificate at startup and accepts any peer (see [Cluster transport trust](#cluster-transport-trust))
 - 🔀 **Multiplexed streams** — concurrent shard transfers without head-of-line blocking
 - ⚡ **Connection pooling** — persistent connections to peer nodes
 - 🌊 **Natural backpressure** — QUIC flow control prevents overloading slow peers
 
 ### Cluster transport trust
 
-The cluster transport does not authenticate nodes. Each node generates a self-signed certificate at startup and accepts any peer's certificate without verifying it. QUIC encrypts the traffic against passive eavesdropping, but not against an attacker on the path. Any host that can reach a node's `quicPort` can join the cluster, sync topology, and read, write, tombstone and purge shards. S3 credentials and bucket policies do not apply to this port.
+Without `cluster.tls` the cluster transport does not authenticate nodes. Each node generates a self-signed certificate at startup and accepts any peer's certificate without verifying it. QUIC encrypts the traffic against passive eavesdropping, but not against an attacker on the path. Any host that can reach a node's `quicPort` can join the cluster, sync topology, and read, write, tombstone and purge shards. S3 credentials and bucket policies do not apply to this port. Run such a cluster only on a network where every host that can reach `quicPort` (UDP, default 4000) is a cluster node: a private network or VPN between the nodes, with `quicPort` firewalled from everything else.
+
+With `cluster.tls` set, the transport is mutual TLS (TLS 1.3, no session resumption, no early data) with a cluster CA you run:
+
+- **Identity.** A node's identity is the single DNS subject alternative name (SAN) of its certificate, and it equals `cluster.nodeId`. With `cluster.tls`, `nodeId` is required and must be a lowercase DNS name such as `node-1` or `node-1.storage.internal`; it is never generated, and it must still match the node id persisted in the control root. One certificate serves as both the server and the client certificate, so it must be valid for both: an extended key usage extension listing `serverAuth` and `clientAuth`, or no extended key usage extension at all (the recipe below issues both). Use a dedicated CA per cluster: every certificate it signs with one lowercase DNS SAN is a member of the cluster.
+- **Checks.** A node connects to a known peer only if the peer's certificate names exactly that peer's node id (one DNS SAN, no wildcard), and to a seed (`seedNodes`, known only by its address) only if the seed presents a certificate from the cluster CA. A node accepts a connection only with a client certificate from the cluster CA, and a join or heartbeat only for the node id that certificate names. A peer without such a certificate fails the handshake before it can send any request. Every CA-signed node is a full member: it may sync topology and read, write, tombstone and purge any shard, so the way to remove a compromised node is to stop trusting its certificate (a new CA, see the rotation below).
+- **Startup.** A node checks its own certificate the way its peers will (chain, validity, server and client authentication, the SAN, and that `keyFile` matches `certFile`) and refuses to start if that check or any file check below fails. The error names the file and the reason. A node never falls back to the unauthenticated transport. At startup it logs one line with its certificate's `notAfter` and the SHA-256 of each CA certificate, and `getClusterHealth().transport` reports them (see [Cluster Health](#cluster-health)).
+- **Files.** `caFile` holds one CA certificate, or two during a CA rotation; anything else is refused, which keeps a system CA bundle out. `certFile` holds the node certificate, optionally followed by intermediates, and nothing but certificates. `keyFile` holds exactly one unencrypted PKCS#8, SEC1 or PKCS#1 key; ECDSA P-256 is recommended. Each path must be absolute and canonical, with no symbolic link anywhere, and lie outside the control root and every drive root (roots are backed up and replaced, and a key must not travel with them). That check compares paths, so a bind mount that makes a root reachable under another path is not detected. Each file must be a regular file of at most 64 KiB. The files and their directories must be owned by the engine's user or by root and must not be group- or world-writable, and `keyFile` must be owned by the engine's user and grant no group or world permission (mode 0600 or 0400).
+- **Reload.** The files are read once at startup; a restart is the reload. Certificates are checked at every handshake, so a connection established before a certificate's `notAfter` keeps running until it reconnects, and new handshakes after `notAfter` fail. Renew certificates and restart the nodes before they expire.
+
+#### Making the CA and the node certificates
+
+The engine ships no CA tooling. With OpenSSL 3 or LibreSSL 3.3 (the `openssl` of macOS), create the CA once and keep `ca.key` offline. `ec_param_enc:named_curve` is required for LibreSSL, which otherwise writes the curve as explicit parameters that the engine refuses; OpenSSL 3 writes the named curve either way:
+
+```bash
+openssl genpkey -algorithm EC -pkeyopt ec_paramgen_curve:P-256 \
+  -pkeyopt ec_param_enc:named_curve -out ca.key
+openssl req -x509 -new -key ca.key -sha256 -days 3650 \
+  -subj "/CN=objectstorage cluster CA" \
+  -addext "basicConstraints=critical,CA:TRUE" \
+  -addext "keyUsage=critical,keyCertSign,cRLSign" \
+  -out ca.pem
+```
+
+Then issue one certificate per node, with the node id as its only DNS SAN:
+
+```bash
+NODE_ID=node-1
+openssl genpkey -algorithm EC -pkeyopt ec_paramgen_curve:P-256 \
+  -pkeyopt ec_param_enc:named_curve -out "$NODE_ID.key"
+openssl req -new -key "$NODE_ID.key" -subj "/CN=$NODE_ID" -out "$NODE_ID.csr"
+cat > "$NODE_ID.ext" <<EXT
+basicConstraints = critical,CA:FALSE
+keyUsage = critical,digitalSignature
+extendedKeyUsage = serverAuth,clientAuth
+subjectAltName = DNS:$NODE_ID
+EXT
+openssl x509 -req -in "$NODE_ID.csr" -CA ca.pem -CAkey ca.key -CAcreateserial \
+  -days 365 -sha256 -extfile "$NODE_ID.ext" -out "$NODE_ID.pem"
+```
+
+Install `ca.pem` and the node's certificate and key on the node, as the user that runs the engine and outside its control and drive roots:
+
+```bash
+install -d -m 0755 /etc/objectstorage/tls
+install -m 0644 ca.pem "$NODE_ID.pem" /etc/objectstorage/tls/
+install -m 0600 "$NODE_ID.key" /etc/objectstorage/tls/
+```
+
+Then set `cluster.tls` to the three paths (see [Configuration](#configuration)). The test suite runs exactly these commands (`test/test.cluster-tls.node.ts`).
 
-Run cluster mode only on a network where every host that can reach `quicPort` (UDP, default 4000) is a cluster node: a private network or VPN between the nodes, with `quicPort` firewalled from everything else. This has been the case since cluster mode was introduced, and 11.0.0 does not change it. Mutual TLS with a cluster CA and certificate-checked joins are planned.
+**Docker secrets** are mounted owned by root with mode 0444 by default, which the key check refuses. Set the key secret's `uid` to the engine's user and its `mode` to `0400` in the service's long `secrets` syntax. Docker Compose ignores `uid`, `gid` and `mode` for secrets read from a file, because it bind-mounts the file; there the host file itself must be owned by the engine's uid with mode 0600 or 0400. Kubernetes secret volumes present their files through symbolic links, which the canonical-path rule refuses.
+
+#### Enabling mutual TLS
+
+Nodes with and without `cluster.tls` cannot talk to each other: a TLS node refuses peers without a client certificate and refuses self-signed servers. Enabling TLS is therefore not a rolling change: stop every node, configure `cluster.tls` on every node, then start every node. A node whose `nodeId` was generated keeps that id (the control root persists it, and `getClusterHealth().nodeId` reports it): configure it as `nodeId` and issue the node's certificate for it, or the node refuses to start. Disabling TLS takes the same full stop.
+
+#### Rotating certificates and the CA
+
+A node certificate is renewed by issuing a new one from the same CA and restarting the node; its peers need no change. A new CA takes three rolling restarts, with no cluster stop:
+
+1. Put both CAs into every node's `caFile` (two certificates) and restart the nodes one at a time.
+2. Issue every node a certificate from the new CA and restart the nodes one at a time.
+3. Remove the old CA from every `caFile` and restart the nodes one at a time.
+
+Every pair of nodes stays connected throughout, because trust only grows before the certificates change and only shrinks after. The order matters: a node with a certificate from the new CA cannot connect to a node that trusts only the old one.
 
 ### Cluster Membership
 
@@ -1847,7 +2016,7 @@ Atomically replace the active runtime credential set without restarting the serv
 
 #### `getClusterHealth(): Promise<IClusterHealth>`
 
-Read the Rust core's current cluster, drive, quorum, and repair health snapshot. Standalone mode returns `{ enabled: false }`.
+Read the Rust core's current cluster, drive, quorum, repair, and transport health snapshot. Standalone mode returns `{ enabled: false }`.
 
 In cluster mode, `quicAddress` is the local QUIC/UDP socket's actual bound
 address. With `cluster.quicPort: 0`, the operating system assigns its port; use
@@ -1855,6 +2024,20 @@ address. With `cluster.quicPort: 0`, the operating system assigns its port; use
 Membership advertisements and peer `quicAddress` values contain that same bound
 address, including after a restart.
 
+#### `getClusterSnapshot(): Promise<IObjectStorageClusterSnapshot>`
+
+The [dashboard](#dashboard)'s snapshot, built by the engine from memory only:
+`local` is this node's `IObjectStorageNodeSnapshot` (counters, totals, drives
+from the last heartbeat probe, healing state, recent events) and, in cluster
+mode, `cluster` adds quorum, the erasure layout and every peer, with the peer's
+own snapshot when it answered within a second. One snapshot runs at a time; a
+call while another runs rejects. Standalone mode returns `cluster: null`.
+
+#### `dashboardPort: number | undefined`
+
+The dashboard's bound TCP port while it runs; `undefined` while it is off or
+stopped.
+
 #### `runHealingScan(options?: IRunHealingScanOptions): Promise<IClusterHealingScanResult>`
 
 Run a healing scan on this cluster node (see [Self-Healing](#self-healing)) and
@@ -1913,7 +2096,7 @@ objectstorage uses a **hybrid Rust + TypeScript** architecture:
 
 **Why Rust?** The original TypeScript implementation had critical perf issues: OOM on multipart uploads (parts buffered in memory), double stream copying, file descriptor leaks on HEAD requests, full-file reads for range requests, and no backpressure. The Rust binary solves these with bounded-memory streaming I/O, backpressure, and direct `seek()` for range requests.
 
-**IPC Protocol:** TypeScript communicates with the `ruststorage` binary over newline-delimited JSON via stdin/stdout. The current management commands are `probeStoragePool`, `findOrphanObjectLeaves`, `getStoragePoolDiagnostic`, `start`, `stop`, `createBucket`, `createBucketTenant`, `ensureBucketTenant`, `deleteBucketTenant`, `rotateBucketTenantCredentials`, `listBucketTenants`, `getBucketTenantCredential`, `getBucketRetentionCapability`, `getBucketRetentionReceipt`, `getBucketMigrationCapability`, `createSourceMigration`, `createDestinationMigration`, `transitionSourceMigration`, `transitionDestinationMigration`, `cleanupSourceMigration`, `inspectBucketMigration`, `exportBucket`, `importBucket`, `deleteBucket`, `commitResourcePublication`, `getResourceFencingCapability`, `getBucketResourceFenceState`, `getStorageStats`, `listBucketSummaries`, `listCredentials`, `replaceCredentials`, `createPrefixCredential`, `revokePrefixCredential`, `listPrefixCredentials`, `getPrefixCredentialStatus`, `getClusterHealth`, and `runHealingScan`. `getStoragePoolDiagnostic` reads a weak, cached diagnostic source and remains responsive while another management command owns the server; it does not retain the mounted root after server ownership completes. `runHealingScan` answers when its scan completes, with the request's `id`; the engine serves other commands meanwhile, and a shutdown answers a pending request with an error before the `stop` response.
+**IPC Protocol:** TypeScript communicates with the `ruststorage` binary over newline-delimited JSON via stdin/stdout. The current management commands are `probeStoragePool`, `findOrphanObjectLeaves`, `getStoragePoolDiagnostic`, `start`, `stop`, `createBucket`, `createBucketTenant`, `ensureBucketTenant`, `deleteBucketTenant`, `rotateBucketTenantCredentials`, `listBucketTenants`, `getBucketTenantCredential`, `getBucketRetentionCapability`, `getBucketRetentionReceipt`, `getBucketMigrationCapability`, `createSourceMigration`, `createDestinationMigration`, `transitionSourceMigration`, `transitionDestinationMigration`, `cleanupSourceMigration`, `inspectBucketMigration`, `exportBucket`, `importBucket`, `deleteBucket`, `commitResourcePublication`, `getResourceFencingCapability`, `getBucketResourceFenceState`, `getStorageStats`, `listBucketSummaries`, `listCredentials`, `replaceCredentials`, `createPrefixCredential`, `revokePrefixCredential`, `listPrefixCredentials`, `getPrefixCredentialStatus`, `getClusterHealth`, `getClusterSnapshot`, and `runHealingScan`. `getStoragePoolDiagnostic` reads a weak, cached diagnostic source and remains responsive while another management command owns the server; it does not retain the mounted root after server ownership completes. `runHealingScan` answers when its scan completes, with the request's `id`; the engine serves other commands meanwhile, and a shutdown answers a pending request with an error before the `stop` response. `getClusterSnapshot` is answered the same deferred way, because a cluster node waits up to a second for each peer.
 
 ### S3-Compatible Operations
 

package/third-party-notices.md

@@ -55,12 +55,28 @@ Developer ID signed or notarized.
 ## Locked Cargo graph
 
 [Cargo dependency notices](./third_party_licenses/cargo-dependencies.html)
-contain the selected license texts and original attributions for 260 packages.
-The complete locked graph also contains three feature-inactive packages:
+contain the selected license texts and original attributions for 279 packages.
+The complete locked graph also contains 18 feature-inactive packages:
 [aho-corasick 1.1.4](./third_party_licenses/aho-corasick-1.1.4-license.txt),
-[valuable 0.1.1](./third_party_licenses/valuable-license.txt) and
+[borsh 1.8.1](./third_party_licenses/borsh-1.8.1-license.txt),
+[borsh-derive 1.8.1](./third_party_licenses/borsh-derive-1.8.1-apache-2.0.txt),
+[dyn-clone 1.0.20](./third_party_licenses/dyn-clone-1.0.20-license.txt),
+[equivalent 1.0.3](./third_party_licenses/equivalent-1.0.3-license.txt),
+[hashbrown 0.17.1](./third_party_licenses/hashbrown-0.17.1-license.txt),
+[indexmap 2.14.2](./third_party_licenses/indexmap-2.14.2-license.txt),
+[proc-macro-crate 3.5.0](./third_party_licenses/proc-macro-crate-3.5.0-license.txt),
+[ref-cast 1.0.27](./third_party_licenses/ref-cast-1.0.27-license.txt),
+[ref-cast-impl 1.0.27](./third_party_licenses/ref-cast-impl-1.0.27-license.txt),
+[schemars 1.2.3](./third_party_licenses/schemars-1.2.3-license.txt),
+[syn 3.0.9](./third_party_licenses/syn-3.0.9-license.txt),
+[toml_datetime 1.1.2](./third_party_licenses/toml_datetime-1.1.2-license.txt),
+[toml_edit 0.25.17](./third_party_licenses/toml_edit-0.25.17-license.txt),
+[toml_parser 1.1.5](./third_party_licenses/toml_parser-1.1.5-license.txt),
+[valuable 0.1.1](./third_party_licenses/valuable-license.txt),
+[winnow 1.0.4](./third_party_licenses/winnow-1.0.4-license.txt) and
 [zerocopy-derive 0.8.47](./third_party_licenses/zerocopy-derive-0.8.47-license.txt).
-Their exact MIT notices bring the inventory to all 261 locked third-party
+Their exact notices (Apache-2.0 for borsh-derive, which offers no MIT
+alternative, MIT for the others) bring the inventory to all 297 locked third-party
 packages, conservatively including build-only, development and inactive targets.
 Listing a package does not claim that it is linked into every distributed executable.
 

package/third_party_licenses/borsh-1.8.1-license.txt

@@ -0,0 +1,23 @@
+Permission is hereby granted, free of charge, to any
+person obtaining a copy of this software and associated
+documentation files (the "Software"), to deal in the
+Software without restriction, including without
+limitation the rights to use, copy, modify, merge,
+publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software
+is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice
+shall be included in all copies or substantial portions
+of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF
+ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
+TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
+PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
+SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR
+IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.

package/third_party_licenses/borsh-derive-1.8.1-apache-2.0.txt

@@ -0,0 +1,201 @@
+                                 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 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 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 those 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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2019 Near
+
+   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.