fileport-gateway 0.1.0

package/docs/CURRENT_ARCHITECTURE.md

@@ -0,0 +1,69 @@
+# Current Architecture
+
+## Scope
+
+This document describes the clean-room Phase 0/1 implementation in this repository. The historical portable kit is reference material only and is not present in this Git history.
+
+## Historical implementation observed (reference only)
+
+The supplied 2026-08-21 portable snapshot was inspected outside this repository. Its implementation combined filesystem serving and product behavior in one Node process:
+
+- `src/cli.ts` owned config, root registration, single TCP server reuse and absolute-path URL generation;
+- `src/server.ts` (~1,500 lines) owned root registry, listing/search, raw file reads, atomic save, PlantUML and routing under `/fileport/api/*`;
+- `src/web/fileport-browser.tsx` (~2,800 lines) owned the artifact UI, editing, Monaco-style source views and renderer integrations;
+- URLs encoded full local absolute paths, while minimum scope depended on registered public roots;
+- no capability token, expiry or revoke lifecycle existed.
+
+No historical source or commit was imported. The new architecture below replaces the filesystem backend with Dufs and introduces an opaque capability boundary. Renderer parity is intentionally staged after the secure Phase 1 transport.
+
+## Runtime topology
+
+```text
+Agent CLI
+  └─ HTTP over $STATE/control.sock (0600)
+       └─ Fileport Gateway :7892
+            ├─ ShareRegistry ($STATE/shares.json, 0600)
+            ├─ capability URL + scope guard
+            ├─ minimal read-only preview shell
+            └─ reverse proxy
+                 └─ official Dufs 0.46.0 worker per canonical root
+                      └─ Unix socket (0600), no TCP listener
+```
+
+## Modules
+
+| Module | Responsibility |
+|---|---|
+| `src/cli.ts` | `serve`, `share`, `ls`, `revoke`; auto-starts Gateway through the local control socket |
+| `src/registry.ts` | persistent capability IDs, canonical targets, expiry filtering, atomic 0600 registry writes |
+| `src/workers.ts` | `canonical root -> Dufs child`, concurrent start deduplication, stale socket recovery, readiness probe and crash restart |
+| `src/paths.ts` | URL decoding, traversal rejection, realpath scope check, symlink escape rejection and sensitive-target guard |
+| `src/proxy.ts` | streaming HTTP/HEAD/Range reverse proxy over Unix sockets |
+| `src/gateway.ts` | public capability routes, local control API, read-only policy and Gateway health |
+| `src/ui.ts` | intentionally small Phase 1 read-only preview shell; no historical UI source was imported |
+
+## URL model
+
+- Public URL: `/s/<192-bit-capability>/`
+- Filesystem path: `/s/<capability>/fs/<relative-path>`
+- Absolute filesystem paths never appear in the URL.
+- A file share permits exactly its one basename.
+- A directory share permits only canonical descendants of that directory.
+- Dufs's root is never trusted as the authorization boundary: every request passes the Gateway scope guard before proxying.
+
+## Security properties in Phase 1
+
+- Dufs has no network listener; each worker binds only a Unix socket.
+- No Dufs upload/delete/allow-all/symlink flags are enabled.
+- Gateway permits only `GET` and `HEAD` for filesystem routes.
+- Traversal, encoded separators, double encoding and symlink escape fail closed.
+- Home, filesystem root and common credential paths/names cannot be shared.
+- Registry, control socket and worker sockets are mode 0600; state directory is 0700.
+- Worker listings hide common credential/VCS patterns as defense in depth.
+- Revoked, expired and unknown capabilities are denied.
+
+## Phase 2 strict RW extension
+
+Phase 2 adds explicit `ro | rw` share permission and optional expiry. Dufs remains read-only. An RW share may use only Fileport's `/api/edit` snapshot endpoint and `/api/save` endpoint for an existing, scoped, allowlisted text file. Saves require an optimistic version, serialize per target, preserve mode, use same-directory fsync + atomic rename, and reject stale/external changes. RO and legacy shares fail closed.
+
+The full Monaco/Graphviz/PlantUML UI, `--line`, VSCode Remote links, and production systemd installation remain later phases.

package/docs/DUFS_COMPATIBILITY.md

@@ -0,0 +1,38 @@
+# Dufs Compatibility Report
+
+## Pinned dependency
+
+- Project: [sigoden/dufs](https://github.com/sigoden/dufs)
+- Version: `0.46.0`
+- Git tag commit: `b69946df232ceca5d24d0067f2beb6b5ed1c292c`
+- Linux x86_64 musl archive SHA256: `817769f726613194bcff9d0e3e481eaccc86ac11208857614f36a8c02f410977`
+- Installation: `scripts/install-dufs.sh`
+- Reproducible contract: `FILEPORT_DUFS_BIN=/path/to/dufs node scripts/dufs-compatibility.mjs`
+
+## Observed contract
+
+| Capability | Result | Evidence/notes |
+|---|---|---|
+| Unix socket bind | PASS | `dufs --bind <socket> <root>` |
+| GET file | PASS | body and status validated |
+| HEAD file | PASS | no body; correct Content-Length |
+| Range | PASS | `bytes=0-4` -> HTTP 206 and exact bytes |
+| directory JSON | PASS | `?json`; response is an object with `paths[]` |
+| filename search JSON | PASS | `?q=<name>&json`; nested match names are relative paths such as `sub/needle.log` |
+| Unicode/space filename | PASS | percent-encoded Chinese filename |
+| 3 MiB file | PASS | exact length |
+| missing/deleted/renamed | PASS | dynamic filesystem state reflected correctly |
+| outside-root symlink | PASS | denied (404) without `--allow-symlink` |
+| unreadable file | GAP | Dufs returns 500; Gateway preflight maps unreadable targets to 403 |
+| write disabled | PASS | PUT returns 403 |
+| dedicated health endpoint | GAP | `/healthz` returns 404 in Dufs 0.46.0 |
+
+Machine-readable evidence is written by the task run to `workfile/fileport-dufs/artifacts/output/dufs-compatibility-v0.46.0.json`.
+
+## Integration decisions
+
+1. Dufs is launched without `--allow-all`, upload, delete, archive or symlink access.
+2. Search is enabled because it is part of Phase 1 compatibility, but all requests still pass Gateway share-scope authorization.
+3. Worker readiness is socket existence plus a real `HEAD /?json` request; no nonexistent Dufs health endpoint is assumed.
+4. Gateway exposes its own `/healthz` including active worker count.
+5. Upgrades require rerunning this exact contract and the Gateway end-to-end suite before changing the pin.

package/docs/MIGRATION_PLAN.md

@@ -0,0 +1,53 @@
+# Migration Plan
+
+## Principle
+
+This repository is a clean-room implementation. The historical Fileport package is behavioral reference only. Dufs stays an original, pinned, replaceable binary; it is not forked.
+
+## Phase 0 — complete
+
+- Pin and checksum official Dufs 0.46.0.
+- Validate Unix socket, GET, HEAD, Range, JSON listing/search, Unicode, large file, symlink behavior, mutation denial and filesystem changes.
+- Record the missing Dufs health endpoint and exact JSON response shape.
+
+## Phase 1 — delivered by this change
+
+- Persistent capability `ShareRegistry`.
+- One read-only Dufs Unix Socket worker per canonical root.
+- Concurrent worker-start deduplication, stale socket recovery and crash restart.
+- Reverse proxy for GET/HEAD/Range.
+- Gateway scope guard independent of Dufs root.
+- Minimal browser preview shell and CLI (`share`, `ls`, `revoke`, `serve`).
+- Gateway health endpoint.
+
+Acceptance invariants:
+
+- no Dufs TCP listener;
+- URL does not contain absolute paths;
+- file share cannot read sibling;
+- directory share cannot escape via traversal, encoding or symlink;
+- same root reuses worker;
+- writes are denied;
+- revoked/expired/unknown shares are denied.
+
+## Phase 2 — strict RW (delivered)
+
+- Explicit `--rw` / `--readonly` and `--expire <Nm|Nh|Nd|Nw>`.
+- Dufs remains read-only.
+- `/api/edit` returns content + optimistic version from one open file handle.
+- `/api/save` updates only an existing allowlisted text file inside share scope.
+- Per-target serialization, stale-version rejection, same-directory temp file, fsync, atomic rename, directory fsync and mode preservation.
+- No create/delete/rename/full filesystem RW.
+- Preview UI exposes Edit/Save only for eligible RW files and requires an explicit browser confirmation.
+
+## Phase 3 — lifecycle and product UI
+
+Add expiry CLI parsing, share inspection, cleanup/reaping, richer artifact renderers, Markdown/source views, `--line`, VSCode Remote link and PlantUML sandbox. Restore behaviors from contracts, not copied historical source.
+
+## Phase 4 — operations
+
+Add user-service packaging, structured logs/metrics, worker idle reclamation, startup reconciliation, release artifacts and signed/checksummed Dufs acquisition. Run compatibility and security tests for every Dufs upgrade.
+
+## Rollback
+
+Phase 1 does not modify or restart any pre-existing Fileport service. It uses an isolated state directory and configurable port. Rollback is stopping this Gateway and removing its task-scoped state; source rollback is a normal Git revert.

package/package.json

@@ -0,0 +1,69 @@
+{
+  "name": "fileport-gateway",
+  "version": "0.1.0",
+  "description": "Secure Agent Artifact Gateway with capability URLs, strict saves, and Dufs-backed file serving.",
+  "type": "module",
+  "bin": {
+    "fileport": "dist/cli.js"
+  },
+  "scripts": {
+    "build": "npm run clean && tsc",
+    "typecheck": "tsc --noEmit",
+    "test": "node --test --import tsx test/*.test.ts",
+    "start": "node dist/cli.js serve",
+    "clean": "node scripts/clean.mjs",
+    "prepack": "npm run build && npm run vendor:dufs",
+    "vendor:dufs": "node scripts/prepare-dufs.mjs",
+    "verify:release": "npm run typecheck && FILEPORT_TEST_DUFS=vendor/dufs npm test && FILEPORT_DUFS_BIN=vendor/dufs node scripts/dufs-compatibility.mjs"
+  },
+  "engines": {
+    "node": ">=22.14.0",
+    "npm": ">=11.5.1"
+  },
+  "devDependencies": {
+    "@types/node": "^22.15.0",
+    "tsx": "^4.20.0",
+    "typescript": "^5.8.0"
+  },
+  "license": "MIT",
+  "files": [
+    "dist/",
+    "docs/",
+    "vendor/dufs",
+    "vendor/LICENSE-DUFS-APACHE",
+    "vendor/LICENSE-DUFS-MIT",
+    "scripts/install-dufs.sh",
+    "scripts/dufs-compatibility.mjs",
+    "README.md",
+    "LICENSE",
+    "THIRD_PARTY_NOTICES.md"
+  ],
+  "author": "not_nil <hanyi.me@foxmail.com>",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/nil-err/fileport.git"
+  },
+  "bugs": {
+    "url": "https://github.com/nil-err/fileport/issues"
+  },
+  "homepage": "https://github.com/nil-err/fileport#readme",
+  "keywords": [
+    "file-sharing",
+    "artifact-preview",
+    "developer-tools",
+    "agent",
+    "dufs",
+    "capability-security",
+    "devbox"
+  ],
+  "os": [
+    "linux"
+  ],
+  "cpu": [
+    "x64"
+  ],
+  "publishConfig": {
+    "access": "public",
+    "provenance": true
+  }
+}

package/scripts/dufs-compatibility.mjs

@@ -0,0 +1,32 @@
+#!/usr/bin/env node
+import assert from "node:assert/strict";
+import { spawn } from "node:child_process";
+import fs from "node:fs/promises";
+import http from "node:http";
+import os from "node:os";
+import path from "node:path";
+
+const dufs=process.env.FILEPORT_DUFS_BIN; if(!dufs) throw new Error("FILEPORT_DUFS_BIN is required");
+const temp=await fs.mkdtemp(path.join(os.tmpdir(),"dufs-contract-")); const root=path.join(temp,"root"); const socket=path.join(temp,"dufs.sock"); await fs.mkdir(path.join(root,"sub"),{recursive:true}); await fs.writeFile(path.join(root,"hello.txt"),"hello world\n"); await fs.writeFile(path.join(root,"中文 文件.txt"),"你好\n"); await fs.writeFile(path.join(root,"sub","needle.log"),"x"); await fs.writeFile(path.join(root,"large.bin"),Buffer.alloc(3*1024*1024,7)); await fs.symlink("/etc/passwd",path.join(root,"outside")); await fs.writeFile(path.join(root,"denied"),"secret",{mode:0o000});
+const child=spawn(dufs,["--bind",socket,"--allow-search",root],{stdio:["ignore","ignore","pipe"]}); let stderr="";child.stderr.on("data",c=>stderr+=c);
+async function waitSocket(){for(let i=0;i<100;i++){try{if((await fs.stat(socket)).isSocket())return;}catch{}await new Promise(r=>setTimeout(r,25));}throw new Error(`socket timeout ${stderr}`)}
+function req(url,method="GET",headers={}){return new Promise((resolve,reject)=>{const q=http.request({socketPath:socket,path:url,method,headers},r=>{const chunks=[];r.on("data",c=>chunks.push(c));r.on("end",()=>resolve({status:r.statusCode,headers:r.headers,body:Buffer.concat(chunks)}));});q.on("error",reject);q.end();});}
+const results=[];async function check(name,fn){try{await fn();results.push({name,status:"PASS"});}catch(error){results.push({name,status:"FAIL",detail:String(error)});}}
+try{await waitSocket();
+ await check("unix socket startup",async()=>assert.ok((await fs.stat(socket)).isSocket()));
+ await check("GET file",async()=>{const x=await req("/hello.txt");assert.equal(x.status,200);assert.equal(x.body.toString(),"hello world\n")});
+ await check("HEAD file",async()=>{const x=await req("/hello.txt","HEAD");assert.equal(x.status,200);assert.equal(x.body.length,0);assert.equal(x.headers["content-length"],"12")});
+ await check("Range",async()=>{const x=await req("/hello.txt","GET",{range:"bytes=0-4"});assert.equal(x.status,206);assert.equal(x.body.toString(),"hello")});
+ await check("directory JSON",async()=>{const x=await req("/?json");assert.equal(x.status,200);const d=JSON.parse(x.body.toString());assert.ok(d.paths.some(v=>v.name==="hello.txt"))});
+ await check("search JSON",async()=>{const x=await req("/?q=needle&json");assert.equal(x.status,200);const d=JSON.parse(x.body.toString());assert.ok(d.paths.some(v=>v.name.endsWith("needle.log")))});
+ await check("unicode filename",async()=>assert.equal((await req("/%E4%B8%AD%E6%96%87%20%E6%96%87%E4%BB%B6.txt")).status,200));
+ await check("large file",async()=>{const x=await req("/large.bin");assert.equal(x.status,200);assert.equal(x.body.length,3*1024*1024)});
+ await check("404",async()=>assert.equal((await req("/missing")).status,404));
+ await check("symlink outside denied",async()=>assert.equal((await req("/outside")).status,404));
+ const denied=await req("/denied"); results.push({name:"permission denied",status:denied.status===403?"PASS":"GAP",detail:`unreadable file returned ${denied.status}; Gateway preflight maps unreadable targets to 403`});
+ await check("write denied",async()=>assert.equal((await req("/new.txt","PUT")).status,403));
+ await check("deleted file",async()=>{await fs.writeFile(path.join(root,"gone"),"x");await fs.unlink(path.join(root,"gone"));assert.equal((await req("/gone")).status,404)});
+ await check("renamed file",async()=>{await fs.writeFile(path.join(root,"old"),"x");await fs.rename(path.join(root,"old"),path.join(root,"new"));assert.equal((await req("/old")).status,404);assert.equal((await req("/new")).status,200)});
+ const health=await req("/healthz");results.push({name:"dedicated health endpoint",status:health.status===200?"PASS":"GAP",detail:`/healthz returned ${health.status}; use socket + GET/HEAD readiness`});
+}finally{child.kill("SIGTERM");await new Promise(r=>child.once("exit",r));await fs.rm(temp,{recursive:true,force:true});}
+console.log(JSON.stringify({dufsVersion:"0.46.0",results},null,2));if(results.some(x=>x.status==="FAIL"))process.exitCode=1;

package/scripts/install-dufs.sh

@@ -0,0 +1,15 @@
+#!/usr/bin/env bash
+set -euo pipefail
+version="0.46.0"
+archive="dufs-v${version}-x86_64-unknown-linux-musl.tar.gz"
+expected="817769f726613194bcff9d0e3e481eaccc86ac11208857614f36a8c02f410977"
+state_home="${XDG_STATE_HOME:-$HOME/.local/state}"
+target="${FILEPORT_DUFS_DIR:-$state_home/fileport/tools}"
+mkdir -p "$target"
+umask 077
+curl -fL "https://github.com/sigoden/dufs/releases/download/v${version}/${archive}" -o "$target/$archive"
+actual="$(sha256sum "$target/$archive" | cut -d' ' -f1)"
+[[ "$actual" == "$expected" ]] || { echo "checksum mismatch: $actual" >&2; exit 1; }
+tar -xzf "$target/$archive" -C "$target" dufs
+chmod 700 "$target/dufs"
+"$target/dufs" --version

package/vendor/LICENSE-DUFS-APACHE

@@ -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 [yyyy] [name of copyright owner]
+
+   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/vendor/LICENSE-DUFS-MIT

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) sigoden(2022)
+
+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.