zedbee 0.1.0-beta.2 → 0.1.0-beta.4

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.
Files changed (267) hide show
  1. package/README.md +8 -2
  2. package/SECURITY.md +7 -2
  3. package/THIRD_PARTY_NOTICES.md +223 -41
  4. package/dist/cache/captured-dependencies.d.ts +4 -4
  5. package/dist/cache/captured-dependencies.d.ts.map +1 -1
  6. package/dist/cache/captured-dependencies.js +11 -2
  7. package/dist/cache/captured-dependencies.js.map +1 -1
  8. package/dist/cache/key.d.ts.map +1 -1
  9. package/dist/cache/key.js +10 -1
  10. package/dist/cache/key.js.map +1 -1
  11. package/dist/checks/adapter.d.ts +6 -0
  12. package/dist/checks/adapter.d.ts.map +1 -1
  13. package/dist/checks/applicability.d.ts.map +1 -1
  14. package/dist/checks/applicability.js +6 -3
  15. package/dist/checks/applicability.js.map +1 -1
  16. package/dist/checks/configuration-presentation.d.ts +1 -1
  17. package/dist/checks/configuration-presentation.d.ts.map +1 -1
  18. package/dist/checks/configuration-presentation.js +12 -4
  19. package/dist/checks/configuration-presentation.js.map +1 -1
  20. package/dist/checks/dead-code/adapter.js +1 -1
  21. package/dist/checks/dead-code/adapter.js.map +1 -1
  22. package/dist/checks/dead-code/captured-filesystem.js +1 -1
  23. package/dist/checks/dead-code/captured-filesystem.js.map +1 -1
  24. package/dist/checks/dead-code/knip-worker.js +8 -0
  25. package/dist/checks/dead-code/knip-worker.js.map +1 -1
  26. package/dist/checks/dead-code/package-metadata.d.ts +6 -0
  27. package/dist/checks/dead-code/package-metadata.d.ts.map +1 -0
  28. package/dist/checks/dead-code/package-metadata.js +33 -0
  29. package/dist/checks/dead-code/package-metadata.js.map +1 -0
  30. package/dist/checks/dead-code/parse-report.d.ts.map +1 -1
  31. package/dist/checks/dead-code/parse-report.js +6 -0
  32. package/dist/checks/dead-code/parse-report.js.map +1 -1
  33. package/dist/checks/dependency-architecture/normalize-graph.d.ts.map +1 -1
  34. package/dist/checks/dependency-architecture/normalize-graph.js +4 -1
  35. package/dist/checks/dependency-architecture/normalize-graph.js.map +1 -1
  36. package/dist/checks/dependency-architecture/rules.d.ts +1 -0
  37. package/dist/checks/dependency-architecture/rules.d.ts.map +1 -1
  38. package/dist/checks/dependency-architecture/rules.js +2 -1
  39. package/dist/checks/dependency-architecture/rules.js.map +1 -1
  40. package/dist/checks/description.d.ts +8 -0
  41. package/dist/checks/description.d.ts.map +1 -1
  42. package/dist/checks/dispatcher.d.ts.map +1 -1
  43. package/dist/checks/dispatcher.js +25 -2
  44. package/dist/checks/dispatcher.js.map +1 -1
  45. package/dist/checks/engine-identity.js +1 -1
  46. package/dist/checks/engine-identity.js.map +1 -1
  47. package/dist/checks/policy-scheduling.d.ts.map +1 -1
  48. package/dist/checks/policy-scheduling.js +6 -4
  49. package/dist/checks/policy-scheduling.js.map +1 -1
  50. package/dist/checks/prettier/adapter.d.ts.map +1 -1
  51. package/dist/checks/prettier/adapter.js +301 -50
  52. package/dist/checks/prettier/adapter.js.map +1 -1
  53. package/dist/checks/prettier/editorconfig.d.ts +14 -0
  54. package/dist/checks/prettier/editorconfig.d.ts.map +1 -0
  55. package/dist/checks/prettier/editorconfig.js +75 -0
  56. package/dist/checks/prettier/editorconfig.js.map +1 -0
  57. package/dist/checks/prettier/project-engine.d.ts +35 -0
  58. package/dist/checks/prettier/project-engine.d.ts.map +1 -0
  59. package/dist/checks/prettier/project-engine.js +611 -0
  60. package/dist/checks/prettier/project-engine.js.map +1 -0
  61. package/dist/checks/prettier/project-inventory.d.ts +12 -0
  62. package/dist/checks/prettier/project-inventory.d.ts.map +1 -0
  63. package/dist/checks/prettier/project-inventory.js +46 -0
  64. package/dist/checks/prettier/project-inventory.js.map +1 -0
  65. package/dist/checks/prettier/project-process.d.ts +13 -0
  66. package/dist/checks/prettier/project-process.d.ts.map +1 -0
  67. package/dist/checks/prettier/project-process.js +38 -0
  68. package/dist/checks/prettier/project-process.js.map +1 -0
  69. package/dist/checks/prettier/project-protocol.d.ts +6 -0
  70. package/dist/checks/prettier/project-protocol.d.ts.map +1 -0
  71. package/dist/checks/prettier/project-protocol.js +271 -0
  72. package/dist/checks/prettier/project-protocol.js.map +1 -0
  73. package/dist/checks/prettier/project-trust.d.ts +32 -0
  74. package/dist/checks/prettier/project-trust.d.ts.map +1 -0
  75. package/dist/checks/prettier/project-trust.js +140 -0
  76. package/dist/checks/prettier/project-trust.js.map +1 -0
  77. package/dist/checks/prettier/project-types.d.ts +94 -0
  78. package/dist/checks/prettier/project-types.d.ts.map +1 -0
  79. package/dist/checks/prettier/project-types.js +2 -0
  80. package/dist/checks/prettier/project-types.js.map +1 -0
  81. package/dist/checks/prettier/project-worker.d.ts +2 -0
  82. package/dist/checks/prettier/project-worker.d.ts.map +1 -0
  83. package/dist/checks/prettier/project-worker.js +393 -0
  84. package/dist/checks/prettier/project-worker.js.map +1 -0
  85. package/dist/checks/prettier/project-workspace.d.ts +21 -0
  86. package/dist/checks/prettier/project-workspace.d.ts.map +1 -0
  87. package/dist/checks/prettier/project-workspace.js +197 -0
  88. package/dist/checks/prettier/project-workspace.js.map +1 -0
  89. package/dist/checks/prettier/settings.d.ts +2 -0
  90. package/dist/checks/prettier/settings.d.ts.map +1 -1
  91. package/dist/checks/prettier/settings.js +1 -0
  92. package/dist/checks/prettier/settings.js.map +1 -1
  93. package/dist/checks/prettier/supported-path.d.ts +3 -0
  94. package/dist/checks/prettier/supported-path.d.ts.map +1 -1
  95. package/dist/checks/prettier/supported-path.js +22 -1
  96. package/dist/checks/prettier/supported-path.js.map +1 -1
  97. package/dist/checks/sanitize-result.d.ts +4 -1
  98. package/dist/checks/sanitize-result.d.ts.map +1 -1
  99. package/dist/checks/sanitize-result.js +57 -0
  100. package/dist/checks/sanitize-result.js.map +1 -1
  101. package/dist/cli.d.ts +4 -0
  102. package/dist/cli.d.ts.map +1 -1
  103. package/dist/cli.js +107 -1
  104. package/dist/cli.js.map +1 -1
  105. package/dist/commands/checks.d.ts +2 -0
  106. package/dist/commands/checks.d.ts.map +1 -1
  107. package/dist/commands/checks.js +65 -3
  108. package/dist/commands/checks.js.map +1 -1
  109. package/dist/commands/doctor.d.ts.map +1 -1
  110. package/dist/commands/doctor.js +4 -0
  111. package/dist/commands/doctor.js.map +1 -1
  112. package/dist/commands/fix.d.ts +6 -0
  113. package/dist/commands/fix.d.ts.map +1 -1
  114. package/dist/commands/fix.js +21 -0
  115. package/dist/commands/fix.js.map +1 -1
  116. package/dist/commands/init.d.ts +10 -2
  117. package/dist/commands/init.d.ts.map +1 -1
  118. package/dist/commands/init.js +370 -10
  119. package/dist/commands/init.js.map +1 -1
  120. package/dist/commands/scan.d.ts +4 -0
  121. package/dist/commands/scan.d.ts.map +1 -1
  122. package/dist/commands/scan.js +29 -0
  123. package/dist/commands/scan.js.map +1 -1
  124. package/dist/commands/telemetry.d.ts +6 -0
  125. package/dist/commands/telemetry.d.ts.map +1 -0
  126. package/dist/commands/telemetry.js +30 -0
  127. package/dist/commands/telemetry.js.map +1 -0
  128. package/dist/config/file-policy.d.ts.map +1 -1
  129. package/dist/config/file-policy.js +31 -8
  130. package/dist/config/file-policy.js.map +1 -1
  131. package/dist/config/load-config.js +1 -1
  132. package/dist/config/load-config.js.map +1 -1
  133. package/dist/config/profiles.d.ts.map +1 -1
  134. package/dist/config/profiles.js +55 -0
  135. package/dist/config/profiles.js.map +1 -1
  136. package/dist/config/schema.d.ts +52 -3
  137. package/dist/config/schema.d.ts.map +1 -1
  138. package/dist/config/schema.js +55 -3
  139. package/dist/config/schema.js.map +1 -1
  140. package/dist/config/settings-registry.js +2 -2
  141. package/dist/config/settings-registry.js.map +1 -1
  142. package/dist/config/summary.d.ts +9 -0
  143. package/dist/config/summary.d.ts.map +1 -0
  144. package/dist/config/summary.js +18 -0
  145. package/dist/config/summary.js.map +1 -0
  146. package/dist/config/target-policy.d.ts +8 -0
  147. package/dist/config/target-policy.d.ts.map +1 -1
  148. package/dist/config/target-policy.js +37 -4
  149. package/dist/config/target-policy.js.map +1 -1
  150. package/dist/core/types.d.ts +15 -0
  151. package/dist/core/types.d.ts.map +1 -1
  152. package/dist/doctor/diagnostics.d.ts +4 -1
  153. package/dist/doctor/diagnostics.d.ts.map +1 -1
  154. package/dist/doctor/diagnostics.js +82 -2
  155. package/dist/doctor/diagnostics.js.map +1 -1
  156. package/dist/fixes/apply-plan.d.ts +5 -0
  157. package/dist/fixes/apply-plan.d.ts.map +1 -1
  158. package/dist/fixes/apply-plan.js +84 -9
  159. package/dist/fixes/apply-plan.js.map +1 -1
  160. package/dist/fixes/build-plan.d.ts +2 -0
  161. package/dist/fixes/build-plan.d.ts.map +1 -1
  162. package/dist/fixes/build-plan.js +7 -0
  163. package/dist/fixes/build-plan.js.map +1 -1
  164. package/dist/fixes/prettier-provider.d.ts +4 -3
  165. package/dist/fixes/prettier-provider.d.ts.map +1 -1
  166. package/dist/fixes/prettier-provider.js +37 -20
  167. package/dist/fixes/prettier-provider.js.map +1 -1
  168. package/dist/fixes/sanitize.d.ts.map +1 -1
  169. package/dist/fixes/sanitize.js +38 -0
  170. package/dist/fixes/sanitize.js.map +1 -1
  171. package/dist/fixes/types.d.ts +3 -0
  172. package/dist/fixes/types.d.ts.map +1 -1
  173. package/dist/fixes/types.js.map +1 -1
  174. package/dist/hooks/detect.d.ts +7 -0
  175. package/dist/hooks/detect.d.ts.map +1 -1
  176. package/dist/hooks/detect.js +140 -17
  177. package/dist/hooks/detect.js.map +1 -1
  178. package/dist/hooks/husky.js +1 -1
  179. package/dist/hooks/husky.js.map +1 -1
  180. package/dist/hooks/install.d.ts +14 -0
  181. package/dist/hooks/install.d.ts.map +1 -0
  182. package/dist/hooks/install.js +146 -0
  183. package/dist/hooks/install.js.map +1 -0
  184. package/dist/hooks/lefthook.js +1 -1
  185. package/dist/hooks/lefthook.js.map +1 -1
  186. package/dist/hooks/raw-git.d.ts.map +1 -1
  187. package/dist/hooks/raw-git.js +5 -0
  188. package/dist/hooks/raw-git.js.map +1 -1
  189. package/dist/hooks/simple-git-hooks.js +1 -1
  190. package/dist/hooks/simple-git-hooks.js.map +1 -1
  191. package/dist/init/prettier-discovery.d.ts +26 -0
  192. package/dist/init/prettier-discovery.d.ts.map +1 -0
  193. package/dist/init/prettier-discovery.js +273 -0
  194. package/dist/init/prettier-discovery.js.map +1 -0
  195. package/dist/init/prettier-editorconfig.d.ts +12 -0
  196. package/dist/init/prettier-editorconfig.d.ts.map +1 -0
  197. package/dist/init/prettier-editorconfig.js +181 -0
  198. package/dist/init/prettier-editorconfig.js.map +1 -0
  199. package/dist/init/prettier-import.d.ts +20 -0
  200. package/dist/init/prettier-import.d.ts.map +1 -0
  201. package/dist/init/prettier-import.js +560 -0
  202. package/dist/init/prettier-import.js.map +1 -0
  203. package/dist/init/recommend.d.ts.map +1 -1
  204. package/dist/init/recommend.js +274 -4
  205. package/dist/init/recommend.js.map +1 -1
  206. package/dist/init/types.d.ts +62 -2
  207. package/dist/init/types.d.ts.map +1 -1
  208. package/dist/init/types.js.map +1 -1
  209. package/dist/init/write-config.d.ts.map +1 -1
  210. package/dist/init/write-config.js +106 -4
  211. package/dist/init/write-config.js.map +1 -1
  212. package/dist/renderers/json.d.ts.map +1 -1
  213. package/dist/renderers/json.js +17 -0
  214. package/dist/renderers/json.js.map +1 -1
  215. package/dist/scan/analysis-session.d.ts +2 -0
  216. package/dist/scan/analysis-session.d.ts.map +1 -1
  217. package/dist/scan/analysis-session.js +3 -0
  218. package/dist/scan/analysis-session.js.map +1 -1
  219. package/dist/scan/run-scan.d.ts +5 -0
  220. package/dist/scan/run-scan.d.ts.map +1 -1
  221. package/dist/scan/run-scan.js +7 -0
  222. package/dist/scan/run-scan.js.map +1 -1
  223. package/dist/scan/source-excerpts.d.ts.map +1 -1
  224. package/dist/scan/source-excerpts.js +12 -0
  225. package/dist/scan/source-excerpts.js.map +1 -1
  226. package/dist/telemetry/client.d.ts +25 -0
  227. package/dist/telemetry/client.d.ts.map +1 -0
  228. package/dist/telemetry/client.js +191 -0
  229. package/dist/telemetry/client.js.map +1 -0
  230. package/dist/telemetry/policy.d.ts +7 -0
  231. package/dist/telemetry/policy.d.ts.map +1 -0
  232. package/dist/telemetry/policy.js +22 -0
  233. package/dist/telemetry/policy.js.map +1 -0
  234. package/dist/telemetry/schema.d.ts +253 -0
  235. package/dist/telemetry/schema.d.ts.map +1 -0
  236. package/dist/telemetry/schema.js +151 -0
  237. package/dist/telemetry/schema.js.map +1 -0
  238. package/dist/telemetry/state.d.ts +148 -0
  239. package/dist/telemetry/state.d.ts.map +1 -0
  240. package/dist/telemetry/state.js +208 -0
  241. package/dist/telemetry/state.js.map +1 -0
  242. package/dist/telemetry/transport.d.ts +6 -0
  243. package/dist/telemetry/transport.d.ts.map +1 -0
  244. package/dist/telemetry/transport.js +22 -0
  245. package/dist/telemetry/transport.js.map +1 -0
  246. package/dist/telemetry/worker.d.ts +4 -0
  247. package/dist/telemetry/worker.d.ts.map +1 -0
  248. package/dist/telemetry/worker.js +45 -0
  249. package/dist/telemetry/worker.js.map +1 -0
  250. package/dist/ui/checks-dashboard.d.ts.map +1 -1
  251. package/dist/ui/checks-dashboard.js +4 -2
  252. package/dist/ui/checks-dashboard.js.map +1 -1
  253. package/dist/ui/init-app.d.ts +7 -4
  254. package/dist/ui/init-app.d.ts.map +1 -1
  255. package/dist/ui/init-app.js +179 -20
  256. package/dist/ui/init-app.js.map +1 -1
  257. package/docs/checks.md +61 -3
  258. package/docs/cli-reference.md +67 -6
  259. package/docs/managed-fixes.md +8 -0
  260. package/docs/privacy.md +118 -1
  261. package/docs/support.md +7 -1
  262. package/licenses/overrides/jscpd-5.3.2-LICENSE +21 -0
  263. package/licenses/overrides/napi-rs-wasm-runtime-1.2.3-LICENSE +43 -0
  264. package/licenses/production-inventory.json +623 -537
  265. package/licenses/reviewed-overrides.json +70 -0
  266. package/package.json +23 -14
  267. package/schema/zedbee.schema.json +192 -73
@@ -6,6 +6,7 @@ Detailed setup, commands, settings, and troubleshooting for Zedbee.
6
6
 
7
7
  - [Setup](#install)
8
8
  - [Commands and local service](#commands)
9
+ - [Usage telemetry](#usage-telemetry)
9
10
  - [Experimental programmatic API](#experimental-programmatic-api)
10
11
  - [Staged code and CI comparisons](#exact-selected-content)
11
12
  - [Configuration](#configuration)
@@ -60,11 +61,30 @@ npx zedbee init
60
61
 
61
62
  Nothing is written until the interactive confirmation. Automation can apply the same proposal with `--yes`; use `--format json` for a deterministic machine-readable preview/result.
62
63
 
64
+ ## Usage telemetry
65
+
66
+ Usage metadata is enabled by default for local commands and CI. Disable it
67
+ before first use with `ZEDBEE_TELEMETRY_DISABLED=1` or `DO_NOT_TRACK=1`, or persist
68
+ a preference with `zedbee telemetry disable`. `zedbee telemetry enable` restores
69
+ the saved preference; environment disable overrides always win.
70
+
71
+ `zedbee telemetry status` explains the effective setting without creating state.
72
+ All three commands support `--format json` and are themselves untracked. The
73
+ setting belongs to the OS user, not the repository, and survives npm upgrades.
74
+ For disposable CI runners, set the disable variable at the pipeline level.
75
+
76
+ CI usage is included and classified separately. Generic `CI` and GitHub/GitLab
77
+ flags are recognized; custom runners may set `ZEDBEE_TELEMETRY_CONTEXT=ci`.
78
+ See [privacy and data handling](privacy.md#usage-telemetry) for exact fields,
79
+ retention, delivery limits and deletion requests. These settings do not change
80
+ OSV scanning or update checks.
81
+
63
82
  ## Commands
64
83
 
65
84
  | Command | Purpose |
66
85
  | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
67
- | `zedbee init` | Recommend checks and safely add `.zedbeerc.jsonc` plus a Husky, Lefthook, simple-git-hooks, or raw Git pre-commit integration |
86
+ | `zedbee init` | Recommend checks and safely add `.zedbeerc.jsonc` plus an optional tracked or local pre-commit hook |
87
+ | `zedbee hooks install` | Activate the tracked hook files in this checkout after installation |
68
88
  | `zedbee scan` | Scan the exact index target, or a committed target with `--base`, and return pass, blocked, or incomplete |
69
89
  | `zedbee fix` | Rescan current staged code, preview managed formatting/lint/React fixes, and apply approved changes to working files only |
70
90
  | `zedbee checks` | Explain every configured check, applicability, targets, engine/license, network use, and limitation without running analysis |
@@ -74,7 +94,7 @@ Nothing is written until the interactive confirmation. Automation can apply the
74
94
 
75
95
  `scan --no-service` and `fix --no-service` use a local executor that closes with the command. Ordinary commands acquire the service only when analysis is needed; empty-index scans and help do not start it. The service stops after five minutes with no active sessions. `service status` and `service stop` support `--format json` for machine-readable state. A service failure makes analysis incomplete; it is never silently retried through another executor.
76
96
 
77
- `init` supports `--profile fast|recommended|thorough`, `--hook auto|husky|lefthook|simple-git-hooks|raw|none`, `--checks <comma-separated IDs>`, `--osv-unavailable block|warn`, `--yes`, and text/JSON output. Interactive setup exposes the same check toggles and OSV outage choice without requiring documentation lookup. `scan`, `checks`, and `doctor` accept `--config <path>`.
97
+ `init` supports `--profile fast|recommended|thorough`, `--hook auto|tracked|husky|lefthook|simple-git-hooks|raw|none`, `--checks <comma-separated IDs>`, `--osv-unavailable block|warn`, `--formatting copy|project|managed|off`, `--trust-project-prettier`, `--yes`, and text/JSON output. Interactive setup exposes check toggles, the formatting choice, the OSV outage choice, and whether to install a hook. If no tracked hook setup is detected, choosing to install a hook also offers **Tracked—shared with teammates** or **Local—this checkout only**. Existing tracked setups are reused without that extra question. `scan`, `checks`, and `doctor` accept `--config <path>`.
78
98
 
79
99
  Bare `zedbee fix` selects `formatting`, `lint`, and `reactCorrectness`; a named
80
100
  selector limits the plan to that supported check. Interactive terminals preview
@@ -90,7 +110,7 @@ remain manual. Review, stage, and rescan after applying; see the
90
110
 
91
111
  Doctor checks snapshot filesystem creation and cleanup separately from background-service execution. The service check starts or reuses the local service, opens a session, formats a small built-in JavaScript string, validates the result, then closes its session and connection. It does not send repository source to the service and leaves the reusable service running. Passing these checks does not establish that a full repository scan will succeed, including large analyzer results. If the service check fails, inspect `zedbee service status` and retry; `zedbee scan --no-service` bypasses the service.
92
112
 
93
- `zedbee checks` uses the same responsive behavior. Checks uses the yellow Zedbee frame with one full-width `CHECKS` panel in a wide interactive terminal, showing each check's severity, applicability, engine, targets, execution details, network use, and limitations. `zedbee checks --format text` forces the complete plain view, while `zedbee checks --format json` keeps the existing deterministic, ANSI-free machine output. Narrow terminals, redirected output, CI, and `TERM=dumb` use plain text; `--no-color` keeps an eligible framed layout without semantic colors.
113
+ `zedbee checks` uses the same responsive behavior. Checks uses the yellow Zedbee frame with one full-width `CHECKS` panel in a wide interactive terminal, showing each check's severity, applicability, engine, targets, execution details, network use, and limitations. Mixed managed/project formatting policies list every detected project root and Prettier version; JSON exposes the same inventory as `effectiveEngines`. `zedbee checks --format text` forces the complete plain view, while `zedbee checks --format json` keeps deterministic, ANSI-free machine output. Narrow terminals, redirected output, CI, and `TERM=dumb` use plain text; `--no-color` keeps an eligible framed layout without semantic colors.
94
114
 
95
115
  ## Experimental programmatic API
96
116
 
@@ -117,6 +137,8 @@ try {
117
137
 
118
138
  Zedbee treats the Git index as the proposed commit. If you stage a file and edit it again without staging the later edit, Zedbee scans the staged version. It materializes isolated baseline and target snapshots by reading the selected Git blobs directly, without checkout EOL conversion, smudge/process filters, or Git LFS materialization, and cleans them after proving execution has stopped. Unproved cleanup retains the snapshots and makes the scan incomplete. Source excerpts therefore come from the exact selected object bytes and line, never from a later working-tree edit.
119
139
 
140
+ `zedbee doctor` inspects configuration and environment without running a scan and, by default, inspects any project Prettier setup as data only. Pass `--trust-project-prettier` to have its formatting probe run the project's installed Prettier through the same installation and snapshot resolution that scans use. `scan` and `fix` accept the same flag: it grants invocation-only consent so a fresh, trusted CI checkout can run project formatting without interactive init; a clean clone without the flag reports the formatting check incomplete instead of executing anything.
141
+
120
142
  A bare `zedbee scan`, along with `zedbee fix` and `zedbee checks`, reads repository configuration from the Git index. `zedbee scan --base <ref>` instead reads it from the committed target `HEAD`. In index mode, a newly staged `.zedbeerc.jsonc` takes effect immediately, while an unstaged or untracked copy cannot weaken the policy applied to staged code; when the selected source has no configuration, Zedbee uses the recommended defaults. `zedbee init` and `zedbee doctor` still inspect the working copy because they create or diagnose local configuration rather than judge a proposed commit.
121
143
 
122
144
  ### Committed branch scans in CI
@@ -208,6 +230,10 @@ Overrides are evaluated in array order for each repository-relative file. Every
208
230
 
209
231
  `pathExclusions` suppresses named checks for exact files or directory globs. Each entry must include at least one repository-relative path, at least one check ID, and a short reason. Exclusions are applied after file overrides, so a matching exclusion always wins for the named checks. Patterns use forward slashes and support ordinary `*`, `**`, and `?` matching; absolute paths, parent traversal, negation, braces, and extended globs are rejected. Other checks still inspect the path. JSON reports include the configured exclusions and identify the ones that matched the selected changes.
210
232
 
233
+ An entry can instead use `"syntax": "gitignore"` with a repository-relative `basePath` (`"."` for the root). Its `files` array then contains ordered ignore-file lines, including comments, directory rules, escapes, and `!` re-inclusions. Each entry is evaluated independently; a re-inclusion cannot undo another entry's exclusion. This syntax uses Prettier's case-insensitive gitignore matching. `init --formatting copy` uses it to preserve project-root `.prettierignore` and `.gitignore` files for formatting only. Repeat copy updates generated entries and preserves handwritten exclusions; switching away from copy removes its generated exclusions. These are saved rules, not live references to the original files.
234
+
235
+ `overrides[].excludeFiles` has a different purpose: it prevents that override from applying while leaving normal checks enabled. Its patterns use the same repository-relative glob syntax as `overrides[].files`.
236
+
211
237
  Run `zedbee checks` to inspect effective settings, their profile or repository source, and configured file overrides without running analysis. Use `zedbee checks --format json` for the complete machine-readable view. `zedbee init` deliberately writes only the selected profile/checks and existing guidance; the shipped editor schema, this documentation, and `zedbee checks` are the settings discovery surface.
212
238
 
213
239
  `reporting.sourceExcerpts` accepts `never`, `interactive`, or `always` and defaults to `interactive`. `never` omits ordinary source from every format, `interactive` includes it only in Ink, and `always` includes it in Ink, text, JSON, and SARIF. An explicit `--include-source` or `--no-source` overrides repository policy for that scan.
@@ -220,9 +246,22 @@ The versioned editor schema ships at `node_modules/zedbee/schema/zedbee.schema.j
220
246
 
221
247
  ## Managed analyzer boundary
222
248
 
223
- Zedbee ships and pins Prettier 3.9.6, ESLint 9.39.5, typescript-eslint 8.67.0, TypeScript 6.0.3, Secretlint 13.0.5, eslint-plugin-react 7.37.5, eslint-plugin-react-hooks 7.1.1, eslint-plugin-jsx-a11y 6.10.2, ast-grep 0.45.1, jscpd 5.0.15, Dependency Cruiser 18.2.0, and Knip 6.32.2. It supplies its own inert analyzer configuration and never loads project ESLint, Prettier, Secretlint, Babel, parser, plugin, or executable analyzer configuration. Rule options follow the analyzer and plugin versions pinned by the installed Zedbee release. Only bundled rules can be configured; custom plugins cannot be loaded. TypeScript configuration is parsed as selected snapshot data, not executed; installed declaration packages may be resolved through the constrained project `node_modules` boundary. Typed lint loads every contained `tsconfig*.json` in an inspected workspace and uses each project for the files it covers. By default, a TypeScript file outside every loaded project makes typed lint incomplete. This avoids validating changed target code under unrelated compiler settings.
249
+ Zedbee ships and pins Prettier 3.9.6, ESLint 9.39.5, typescript-eslint 8.67.0, TypeScript 6.0.3, Secretlint 13.0.5, eslint-plugin-react 7.37.5, eslint-plugin-react-hooks 7.1.1, eslint-plugin-jsx-a11y 6.10.2, ast-grep 0.45.1, jscpd 5.3.2, Dependency Cruiser 18.2.0, and Knip 6.32.2. It supplies its own inert analyzer configuration and never loads project ESLint, Secretlint, Babel, parser, plugin, or executable analyzer configuration; project Prettier runs only when a project formatting engine is explicitly trusted, as described in the [check guide](checks.md#formatting-engines). Rule options follow the analyzer and plugin versions pinned by the installed Zedbee release. Only bundled rules can be configured; custom plugins cannot be loaded. TypeScript configuration is parsed as selected snapshot data, not executed; installed declaration packages may be resolved through the constrained project `node_modules` boundary. Typed lint loads every contained `tsconfig*.json` in an inspected workspace and uses each project for the files it covers. By default, a TypeScript file outside every loaded project makes typed lint incomplete. This avoids validating changed target code under unrelated compiler settings.
250
+
251
+ Zedbee does not load any native analyzer config files, including native Prettier and ESLint configs. The only exception is a project formatting engine that was explicitly trusted as described in the [check guide](checks.md#formatting-engines); every other analyzer keeps the managed boundary. Adoption therefore has a deliberate tradeoff: teams with native configs may see different Zedbee results because those files are not loaded. Re-express the supported policy in `.zedbeerc.jsonc`, within Zedbee's bounded managed settings, rather than expecting native configuration parity. Generated package-manager lockfiles are excluded from formatting scans and fixes, but remain eligible for other supported checks; see [formatting settings](checks.md#prettier-settings).
224
252
 
225
- Zedbee does not load any native analyzer config files, including native Prettier and ESLint configs. Adoption therefore has a deliberate tradeoff: teams with native configs may see different Zedbee results because those files are not loaded. Re-express the supported policy in `.zedbeerc.jsonc`, within Zedbee's bounded managed settings, rather than expecting native configuration parity.
253
+ For commands used in package scripts, Knip reads the installed dependency's
254
+ `package.json` command names as data. This lets it connect commands such as
255
+ `project-check` to the dependency that provides them, including workspace-local
256
+ and root installations. It does not execute those commands, install packages,
257
+ or load their code or plugins. Missing installed metadata can limit command
258
+ recognition. Changes to this metadata invalidate saved dead-code results.
259
+
260
+ Zedbee treats its own entry in `dependencies` or `devDependencies` as intentional
261
+ use, including in workspace packages. You can run it directly from the terminal;
262
+ no hook, package-script alias, or source import is required. This exception applies
263
+ only to unused-dependency findings for the package named `zedbee`. Other unused
264
+ dependencies, undeclared imports, vulnerabilities, and other checks are unchanged.
226
265
 
227
266
  Project checks inspect a workspace as a whole, then compare the isolated selected baseline and target snapshots so existing debt remains non-blocking. This roughly doubles analyzer work. Zedbee runs Knip in a fresh internal worker for each snapshot side, using a captured filesystem shared by Knip and its pinned Oxc WebAssembly resolver. Framework plugins and executable project configs remain disabled. Dynamic imports, framework conventions, wildcard package exports, and TypeScript path aliases may need future managed profiles. Package import aliases (`#name`) in the selected `package.json` are supported, including exact mappings, wildcard mappings, conditions, and fallback arrays. They use the nearest package manifest and the same scan boundary as other imports: an alias cannot bypass checks against installed packages outside the snapshot inventory. Missing aliases remain normal Knip findings; unsafe targets make the dead-code check incomplete. Knip findings can be cached when complete input metadata is available, including the absence checks that protect package resolution. jscpd runs as a subprocess and receives an exact source-file list; exceptionally large workspaces can exceed the operating system argument limit and fail incomplete. Dependency Cruiser runs through its public API.
228
267
 
@@ -294,9 +333,31 @@ Interrupted scans wait for execution cleanup before removing temporary snapshots
294
333
 
295
334
  ## Hooks
296
335
 
336
+ Interactive setup asks whether to install a pre-commit hook. With no existing
337
+ tracked setup, you can choose a tracked hook for the team or a local hook for
338
+ this checkout. A new tracked setup adds hook files and an installer under
339
+ `.husky/`, plus a `prepare` step in `package.json`. Existing `prepare` commands
340
+ are preserved. Review and commit those changes; normal dependency installation
341
+ then activates the hook for teammates. Installation with scripts disabled does
342
+ not activate hooks; run `npx --no-install zedbee hooks install` afterward if needed.
343
+ The installer skips CI, `HUSKY=0`, and directories without Git metadata; the
344
+ tracked prepare script also skips when Zedbee is absent in a production-only
345
+ install. Setup itself does not download dependencies or run project scripts.
346
+
347
+ New tracked setup requires a root `package.json` and refuses to replace custom
348
+ local hooks whose execution cannot be preserved. Interactive setup keeps Local
349
+ and No available when tracked setup is unavailable. Automatic edits of non-shell
350
+ pre-commit scripts are refused; integrate Zedbee through their existing tooling.
351
+ Noninteractive `--hook auto --yes` retains the detected integration or uses a
352
+ local hook. Use `--hook tracked --yes` to explicitly request tracked setup.
353
+
354
+ A local hook stays in Git's private checkout files. It is not shared by a
355
+ commit, push, or clone, so each teammate must opt in separately. Either kind
356
+ can be bypassed by Git options; neither makes checks mandatory on a server.
357
+
297
358
  `zedbee init --hook auto` detects Husky, Lefthook, simple-git-hooks, or raw Git hooks. It preserves unrelated commands, shows exact before/after hashes and diffs, refuses symlink targets, writes atomically, and rolls back earlier writes if a later write fails. Linked worktrees resolve the real Git hook path instead of assuming `.git` is a directory.
298
359
 
299
- Generated hooks run `npx --no-install zedbee scan`. This prevents an unexpected network download during a commit, but it means Zedbee must remain installed in the project. Run `zedbee init` again to preview an idempotent update; an existing Zedbee invocation is not duplicated.
360
+ Newly generated hooks run `npx --no-install zedbee scan --hook-invocation`. The marker distinguishes hook usage in telemetry; it does not change scan behavior. Existing unmarked invocations remain valid and are not rewritten just to add the marker. This prevents an unexpected network download during a commit, but it means Zedbee must remain installed in the project. Run `zedbee init` again to preview an idempotent update; an existing Zedbee invocation is not duplicated.
300
361
 
301
362
  ## Cache and performance
302
363
 
@@ -56,6 +56,14 @@ semantics: it formats the complete current working file, including unstaged
56
56
  work in that file. Select `lint` or `reactCorrectness` alone when whole-file
57
57
  formatting is not wanted.
58
58
 
59
+ When formatting uses `engine: "project"`, the same working-file semantics apply
60
+ but the bytes come from the selected project's installed Prettier, configuration,
61
+ and plugins rather than the bundled engine. A fix plan records the engine, the
62
+ validated installation identity, and the selected snapshot. Applying it
63
+ rechecks local trust and those identities; if the installation or the selected
64
+ staged snapshot changed, the plan is reported stale and the working file is left
65
+ untouched. There is no managed fallback for a project-formatting failure.
66
+
59
67
  For a file that receives both kinds, exact fixes run before selected
60
68
  formatting. This preserves one deterministic order:
61
69
 
package/docs/privacy.md CHANGED
@@ -1,5 +1,113 @@
1
1
  # Privacy and Data Handling
2
2
 
3
+ ## Usage telemetry
4
+
5
+ Zedbee CLI usage telemetry is **enabled by default**, including in CI. Interactive
6
+ `zedbee init` includes an **Enable usage tracking** checkbox near the end of setup:
7
+ “Share anonymous usage data to help us improve Zedbee Swarm.” It starts checked
8
+ unless you have already opted out. Applying setup saves the choice for this local
9
+ installation; cancelling leaves it unchanged. Setup sends no event before the
10
+ choice is saved. No standalone startup notice is printed.
11
+
12
+ Environment opt-outs override the checkbox. Noninteractive `init --yes` preserves
13
+ your existing preference. To disable collection before first use, set `ZEDBEE_TELEMETRY_DISABLED=1` or `DO_NOT_TRACK=1`. You can also
14
+ persist a local preference:
15
+
16
+ ```bash
17
+ npx zedbee telemetry disable
18
+ npx zedbee telemetry status
19
+ npx zedbee telemetry enable
20
+ ```
21
+
22
+ These management commands are not tracked. `status --format json` provides the
23
+ effective setting, its reason, detected environment and any existing local ID.
24
+ Environment disable overrides win over a saved enable preference. `init --yes`,
25
+ package updates and reinstallations do not reset your saved opt-out. Removing
26
+ your user state directory removes the preference. Repository configuration
27
+ cannot enable telemetry for someone who disabled it.
28
+
29
+ Only explicit metadata is sent to `https://telemetry.zedbee.dev/v1/events`, a
30
+ Cloudflare collector forwarding approved events to hosted PostHog:
31
+
32
+ - command/event names, random event/run IDs, UTC timestamp and duration;
33
+ - Zedbee version, Node major version, OS family and CPU architecture;
34
+ - detected CI provider, generated-hook marker, staged/base scan mode and output format;
35
+ - scan outcome, whether input was empty, built-in profile/custom indicator,
36
+ configured enabled check IDs, executed check IDs and finding count;
37
+ - setup outcome/profile/hook type, or fix outcome and aggregate applied/skipped counts;
38
+ - a random user-local installation ID for local commands, or an ephemeral random
39
+ command ID for CI. No persistent local ID is sent by detected CI invocations.
40
+
41
+ Source code, paths, file hashes, reports, snippets, raw errors, secrets,
42
+ dependency names, repository URLs/names, branch names, Git identities, hostnames
43
+ and environment-variable contents are not collected. No npm-install script
44
+ sends telemetry. Help, internal service/hook-management commands and the
45
+ programmatic API do not initialize telemetry. `check_ids` describes executed,
46
+ non-skipped checks; `enabled_check_ids` describes checks enabled globally or by
47
+ any configured file override, even on empty input or when checks are skipped.
48
+ Scan profiles are `fast`, `recommended`, `thorough`, or `custom` when resolved
49
+ check settings differ from the selected built-in profile, or file overrides or
50
+ path exclusions customize the suite. Explicit settings matching built-in defaults
51
+ retain that profile. This summary uses the policy already resolved from the
52
+ Git index (staged scans) or target
53
+ commit (base scans); no settings or paths are sent. It is omitted if configuration
54
+ cannot be resolved. Setup profiles describe setup choices.
55
+
56
+ CI is detected from `CI`, `GITHUB_ACTIONS` and `GITLAB_CI`; custom runners can set
57
+ `ZEDBEE_TELEMETRY_CONTEXT=ci`. Detection is best-effort. No terminal or redirected
58
+ output alone does not imply CI. Set the disable override pipeline-wide when you
59
+ do not want disposable runners to collect usage. CI activity is reported
60
+ separately from local installation counts. Neither is an exact count of people.
61
+
62
+ Local settings and the bounded event outbox are stored under
63
+ `$XDG_STATE_HOME/zedbee/telemetry` when that variable is absolute, otherwise
64
+ `~/.local/state/zedbee/telemetry`. The outbox holds at most 100 events / 256 KiB
65
+ for up to seven days; expired events are discarded during subsequent activity
66
+ and are not sent. Files request owner-only POSIX permissions; Windows relies
67
+ on the user directory's access controls. Unreadable/corrupt preferences suppress
68
+ collection. Lock contention, offline requests and collection failures never
69
+ change command results. Local sending happens in a short-lived detached process;
70
+ CI uses memory only and waits at most one additional second on normal exit.
71
+ Interrupted commands do not wait for telemetry. JSON/SARIF stdout is unchanged.
72
+
73
+ The collector does not forward your source IP or user-agent to PostHog and
74
+ requests no geographic enrichment. Local usage creates a PostHog person profile
75
+ keyed by the random installation ID so its associated events can be deleted.
76
+ No name or email address is collected or added to that profile. CI events do not
77
+ create person profiles. Cloudflare necessarily
78
+ receives connection metadata and may use the IP briefly for abuse limiting.
79
+ Random persistent identifiers are pseudonymous, not a guarantee of anonymity.
80
+ The collector can discard events by metadata rules or quotas; it does not use
81
+ those controls to collect additional categories of information.
82
+
83
+ The initial deployment uses PostHog Free, which provides a one-year event-query
84
+ window. That window is not a guarantee of physical deletion after one year;
85
+ account retention and event-deletion procedures must be verified before the
86
+ telemetry-enabled release. Disabling clears queued local events but cannot
87
+ recall requests already in flight or delete data previously received. For a
88
+ request to remove local-ID-associated data, contact
89
+ [security@zedbee.dev](mailto:security@zedbee.dev) privately with only the local
90
+ telemetry ID shown by `zedbee telemetry status`.
91
+
92
+ Run these commands on the same computer and operating-system user account where
93
+ you used Zedbee:
94
+
95
+ ```sh
96
+ npx zedbee telemetry disable
97
+ npx zedbee telemetry status
98
+ ```
99
+
100
+ Send only the value labeled **Local telemetry ID**. Disabling telemetry preserves
101
+ that ID and stops future collection; it does not delete previously received data.
102
+ Repeat this for each computer or user account you used. If you removed the saved
103
+ telemetry state, the old ID cannot be reconstructed. Do not send source,
104
+ credentials or reports. Ephemeral CI IDs cannot be associated with a person for a targeted
105
+ per-person deletion request. Provider backups follow the provider's deletion
106
+ policy.
107
+
108
+ Telemetry controls are separate from OSV vulnerability scanning and update
109
+ notifications; disabling telemetry does not disable either of those features.
110
+
3
111
  ## Local snapshot processing
4
112
 
5
113
  Index mode materializes two temporary representations: committed `HEAD` and the exact staged Git index. It does not scan later unstaged working-tree edits. Source excerpts are read from that exact index snapshot, so an excerpt cannot be replaced by later working-tree content. An intent-to-add entry supplies no staged file content and is excluded as unstaged. Staged Git LFS pointers and submodule pointers cannot be inspected and make the scan incomplete. Binary assets remain allowed, but binary paths selected by enabled source, formatting, or vulnerability checks are incomplete rather than silently skipped. Every affected path is reported; intentional suppression is configurable with `pathExclusions`.
@@ -8,7 +116,7 @@ Explicit base mode (`scan --base <ref>`) instead materializes the unique merge-b
8
116
 
9
117
  Snapshot paths are validated under a Zedbee-owned temporary directory, selected repository links may not escape it, and cleanup is attempted before the command returns once execution has stopped. Unproved execution cleanup retains snapshots and makes the scan incomplete. Cleanup failure may disclose one validated Zedbee temporary directory so the invoking human or agent can inspect exactly what remains; resolve the execution/cleanup problem before removing it. If Zedbee cannot safely validate the directory's identity, it reports no path and instead directs the operator to inspect the OS temporary directory for stale `zedbee-snapshot-*` directories. Correct permissions, locks, or filesystem problems before retrying: a persistent cause can make later cleanups fail and leave additional snapshots.
10
118
 
11
- Local analyzers receive protected snapshot paths, selected checked source bytes, and managed inert configuration. Zedbee does not run package-manager lifecycle scripts, project commands, remediation, or executable project analyzer configuration.
119
+ Local analyzers receive protected snapshot paths, selected checked source bytes, and managed inert configuration. Zedbee does not run package-manager lifecycle scripts, project commands, or remediation. The sole executable project-configuration exception is explicitly trusted project Prettier mode, described below.
12
120
 
13
121
  TypeScript and typed lint can also capture supporting dependency inputs through constrained installed project `node_modules` and bundled TypeScript resolution boundaries. These are permitted local dependency reads outside the selected source snapshots. Captured content supports analysis in memory; only validated input fingerprints and normalized observations may enter the scan cache. Knip's captured inputs remain snapshot-only. Setup and diagnostics (`init` and `doctor`) may read working-copy configuration.
14
122
 
@@ -34,6 +142,15 @@ selected Prettier formatting intentionally processes the complete current
34
142
  working file, so it can reformat unstaged work. Review the working-tree diff
35
143
  before staging anything.
36
144
 
145
+ When a project's formatting engine is trusted, that project's Prettier,
146
+ configuration, and plugins run in a dedicated child process over a disposable
147
+ mirror of the selected snapshot. The mirror and worker are owned by the scan or
148
+ fix and are removed afterward; project-format results are not persisted in the
149
+ observation cache. Trusted plugin and configuration code can still read files or
150
+ use the network with the user's permissions, so consent is an ongoing decision.
151
+ Configured connection tokens and `NODE_OPTIONS`/`NODE_PATH` are not inherited by
152
+ the worker.
153
+
37
154
  ## Secrets
38
155
 
39
156
  Secrets are always redacted, including when source excerpts are enabled by repository policy or CLI override. Zedbee passes changed snapshot text directly to Secretlint's in-process API with its own fixed preset; it never loads `.secretlintrc` or executable project configuration. Secretlint results are immediately reduced to rule and location metadata. Raw secret text, match text, upstream messages, author data, and source lines never cross into Zedbee findings, events, text, JSON, source excerpts, or stable IDs. To distinguish a different secret replacing existing debt at the same rule and location, Zedbee computes a per-scan HMAC over the exact source range with a random key. The digest and key are ephemeral and are not rendered, cached, or persisted.
package/docs/support.md CHANGED
@@ -94,7 +94,13 @@ If the upgrading command is interrupted, existing sessions can still finish, but
94
94
 
95
95
  Unix service sockets require a sufficiently short canonical OS temporary path and owner-only permissions; Windows uses owner-restricted local named pipes and native process jobs. An unsuitable temporary directory or unverifiable identity fails closed. Use `--no-service` when a service cannot operate in the current environment. Missing permissions, rejected native cleanup, a disconnected client or a socket closing are never treated as proof that analysis stopped: unproved cleanup retains snapshots and reports incomplete.
96
96
 
97
- Zedbee does not load a project's native analyzer config. Prettier, ESLint, React, Hooks, and JSX accessibility behavior comes from Zedbee's managed settings and bundled rules; custom plugins and executable project configuration are outside the supported boundary. Rule options follow the analyzer and plugin versions pinned by the installed Zedbee release and can change when Zedbee upgrades its managed engines. `zedbee checks` displays effective settings and a primary managed engine summary, not every supporting package version.
97
+ Zedbee does not load a project's native analyzer config unless a project formatting engine is explicitly trusted (see [formatting engines](checks.md#formatting-engines)). Prettier, ESLint, React, Hooks, and JSX accessibility behavior comes from Zedbee's managed settings and bundled rules; custom plugins and executable project configuration are outside the supported boundary, except that trusted project mode runs the project's own Prettier, configuration, and plugins at the supported version boundary. Rule options follow the analyzer and plugin versions pinned by the installed Zedbee release and can change when Zedbee upgrades its managed engines. `zedbee checks` displays effective formatting settings and reports the detected project Prettier version whenever the root policy or a path override selects the project engine.
98
+
99
+ Trusted project formatting supports declared Prettier 3 installations resolved through ordinary npm or Yarn `node_modules` layouts and pnpm installations whose repository link points into the pnpm store. Yarn Plug'n'Play, custom Prettier wrapper commands, and CLI-only options such as a custom `--ignore-path` are not reproduced. Configuration files and relative helpers must be contained in the selected Git snapshot; a configuration resolved outside the disposable mirror is rejected before it is imported. Project mode uses the project's root `.prettierignore` and `.gitignore`. Copy mode imports project-root ignore files once as formatting-only exclusions; custom ignore paths are not imported, and later changes to the original ignore files are not synchronized.
100
+
101
+ Relative snapshot symlinks to contained regular files, including configuration files and link chains, are preserved in the disposable mirror. Absolute, escaping, broken, cyclic, and directory snapshot links make project formatting incomplete rather than silently dropping their configuration or reading live files.
102
+
103
+ The project formatter receives a reduced environment and a temporary `HOME`, but it is not an operating-system sandbox. Configuration and plugins still run with the invoking account's filesystem and network permissions, and their behavior can vary with Node.js, the operating system, environment variables, or external services. Only enable project formatting after reviewing the code selected by the scan. CI should grant `--trust-project-prettier` only in a trusted workflow and must not add it automatically for unreviewed pull-request code.
98
104
 
99
105
  This boundary is an adoption tradeoff: teams with native configs may see different Zedbee results because those files are not loaded. Configure supported differences in `.zedbeerc.jsonc` and use the shipped schema for editor validation. `zedbee checks` shows the effective settings, profile or repository source, and ordered overrides without running analysis.
100
106
 
@@ -0,0 +1,21 @@
1
+ The MIT License (MIT)
2
+
3
+ Copyright (c) 2013-2024 Andrey Kucherenko
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
@@ -0,0 +1,43 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2020-present LongYinan
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
22
+
23
+ MIT License
24
+
25
+ Copyright (c) 2018 GitHub
26
+
27
+ Permission is hereby granted, free of charge, to any person obtaining a copy
28
+ of this software and associated documentation files (the "Software"), to deal
29
+ in the Software without restriction, including without limitation the rights
30
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
31
+ copies of the Software, and to permit persons to whom the Software is
32
+ furnished to do so, subject to the following conditions:
33
+
34
+ The above copyright notice and this permission notice shall be included in all
35
+ copies or substantial portions of the Software.
36
+
37
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
38
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
39
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
40
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
41
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
42
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
43
+ SOFTWARE.