yadflow 4.10.0 → 4.12.0

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 (120) hide show
  1. package/CHANGELOG.md +152 -0
  2. package/README.md +14 -3
  3. package/bin/commands.mjs +7 -1
  4. package/bin/yad.mjs +163 -16
  5. package/cli/agent-guard-worker.mjs +13 -0
  6. package/cli/agent-guard.mjs +1053 -57
  7. package/cli/agent-rules.mjs +59 -3
  8. package/cli/argv-flags.mjs +2 -2
  9. package/cli/brain/vendor/LICENSE-graphology-library.txt +21 -0
  10. package/cli/brain/vendor/LICENSE-graphology.txt +21 -0
  11. package/cli/brain/vendor/LICENSE-sigma.txt +12 -0
  12. package/cli/brain/vendor/graphology-library.min.js +2 -0
  13. package/cli/brain/vendor/graphology.umd.min.js +2 -0
  14. package/cli/brain/vendor/sigma.min.js +1369 -0
  15. package/cli/brain/view/app.js +382 -0
  16. package/cli/brain/view/index.html +63 -0
  17. package/cli/brain/view/live.css +228 -0
  18. package/cli/brain/view/live.html +110 -0
  19. package/cli/brain/view/live.js +884 -0
  20. package/cli/brain/view/style.css +141 -0
  21. package/cli/brain-about.mjs +206 -0
  22. package/cli/brain-activity.mjs +285 -0
  23. package/cli/brain-skills.mjs +118 -0
  24. package/cli/brain-vendor.mjs +71 -0
  25. package/cli/brain-view.mjs +345 -0
  26. package/cli/brain.mjs +810 -0
  27. package/cli/brand-cmd.mjs +326 -0
  28. package/cli/brand.mjs +327 -0
  29. package/cli/ci-check.mjs +3 -3
  30. package/cli/doctor.mjs +145 -14
  31. package/cli/epic-state.mjs +93 -1
  32. package/cli/epic.mjs +15 -3
  33. package/cli/errors.mjs +2 -1
  34. package/cli/find-product.mjs +69 -15
  35. package/cli/foundation-publish.mjs +256 -0
  36. package/cli/gate.mjs +29 -3
  37. package/cli/git-read.mjs +38 -0
  38. package/cli/guard-stream.mjs +409 -0
  39. package/cli/guide.mjs +26 -3
  40. package/cli/hook.mjs +59 -9
  41. package/cli/issues-act.mjs +57 -13
  42. package/cli/issues-write.mjs +19 -6
  43. package/cli/issues.mjs +69 -24
  44. package/cli/lib.mjs +37 -2
  45. package/cli/local-page.mjs +138 -0
  46. package/cli/local-setup-record.mjs +71 -0
  47. package/cli/local-setup-steps.mjs +186 -0
  48. package/cli/local-setup.mjs +611 -0
  49. package/cli/machine.mjs +1 -1
  50. package/cli/manifest.mjs +55 -0
  51. package/cli/map/view/app.js +712 -0
  52. package/cli/map/view/index.html +50 -0
  53. package/cli/map/view/style.css +142 -0
  54. package/cli/map-view.mjs +190 -0
  55. package/cli/map.mjs +637 -0
  56. package/cli/members.mjs +9 -15
  57. package/cli/next.mjs +1 -1
  58. package/cli/openpr.mjs +2 -2
  59. package/cli/plain-text.mjs +22 -0
  60. package/cli/plan.mjs +310 -36
  61. package/cli/platform.mjs +5 -5
  62. package/cli/product-index.mjs +1 -1
  63. package/cli/protection.mjs +32 -0
  64. package/cli/reconcile.mjs +61 -13
  65. package/cli/report.mjs +9 -3
  66. package/cli/reports-dir.mjs +393 -0
  67. package/cli/reports.mjs +65 -0
  68. package/cli/run-checks.mjs +5 -2
  69. package/cli/scan.mjs +4 -6
  70. package/cli/secret-text.mjs +66 -0
  71. package/cli/setup.mjs +54 -8
  72. package/cli/standup.mjs +94 -72
  73. package/cli/status.mjs +6 -5
  74. package/cli/test-agents-file.mjs +614 -8
  75. package/cli/test-brain-activity.mjs +753 -0
  76. package/cli/test-brain-view.mjs +381 -0
  77. package/cli/test-brain.mjs +795 -0
  78. package/cli/test-brand.mjs +558 -0
  79. package/cli/test-guide.mjs +438 -0
  80. package/cli/test-local-setup.mjs +1188 -0
  81. package/cli/test-machine.mjs +59 -0
  82. package/cli/test-map.mjs +615 -0
  83. package/cli/test-reports.mjs +382 -0
  84. package/cli/test-run-checks.mjs +4 -0
  85. package/cli/test-worktree.mjs +24 -3
  86. package/cli/toolbox-connect.mjs +21 -6
  87. package/cli/toolbox.mjs +74 -5
  88. package/cli/update-commit.mjs +118 -9
  89. package/cli/usage.mjs +17 -7
  90. package/cli/workspace.mjs +11 -2
  91. package/package.json +8 -4
  92. package/skills/sdlc/module-help.csv +1 -0
  93. package/skills/yad-architecture/SKILL.md +22 -4
  94. package/skills/yad-brand/SKILL.md +69 -0
  95. package/skills/yad-change/SKILL.md +3 -1
  96. package/skills/yad-change/references/triage.md +2 -0
  97. package/skills/yad-checks/SKILL.md +2 -0
  98. package/skills/yad-checks/references/check-gates.md +8 -5
  99. package/skills/yad-checks/templates/checks/build-test-lint.sh +7 -0
  100. package/skills/yad-checks/templates/checks/install-deps.sh +6 -0
  101. package/skills/yad-checks/templates/checks/package-manager.sh +42 -0
  102. package/skills/yad-checks/templates/github/yad-checks.yml +3 -2
  103. package/skills/yad-checks/templates/gitlab/yad-checks.gitlab-ci.yml +3 -2
  104. package/skills/yad-checks/templates/hooks/local-setup-notice.mjs +96 -0
  105. package/skills/yad-checks/templates/hooks/yad-activity.mjs +238 -0
  106. package/skills/yad-connect-repos/SKILL.md +14 -0
  107. package/skills/yad-discovery/SKILL.md +11 -0
  108. package/skills/yad-discovery/references/foundation-schema.md +11 -0
  109. package/skills/yad-docs/templates/app/package-lock.json +18 -10
  110. package/skills/yad-docs/templates/app/package.json +6 -1
  111. package/skills/yad-epic/SKILL.md +3 -0
  112. package/skills/yad-epic/references/state-schema.md +35 -1
  113. package/skills/yad-guide/SKILL.md +10 -7
  114. package/skills/yad-implement/SKILL.md +76 -15
  115. package/skills/yad-issues/SKILL.md +2 -1
  116. package/skills/yad-pr-template/templates/checks/pr-template.sh +8 -4
  117. package/skills/yad-pr-template/templates/checks/pr-title.sh +8 -4
  118. package/skills/yad-spec/SKILL.md +19 -0
  119. package/skills/yad-stories/SKILL.md +22 -4
  120. package/skills/yad-stories/references/story-schema.md +1 -1
@@ -92,6 +92,15 @@ export const COMMAND_CLASS = {
92
92
  // records the team's choice — a team-wide file, as `toolbox add` writes — so only on the person's yes to
93
93
  // the question the read gave (the connect-tool rule); --replace changes the team's current tool.
94
94
  'toolbox connect': { class: 'read', flags: { verify: 'on-request', replace: 'on-request' } },
95
+ // E185: `list` reads the Product's local setup script and runs yad's own checks for this machine; `done` and
96
+ // `skip` record this machine's answers inside .git. None runs a step. A no is the person's: `skip` on request.
97
+ 'local-setup done': { class: 'local-write' },
98
+ 'local-setup list': { class: 'read' },
99
+ 'local-setup skip': { class: 'on-request' },
100
+ // E185 part 3: add and remove write the team's steps into the committed script, which reaches every member's
101
+ // agent — so only when the person asks, as `toolbox add`.
102
+ 'local-setup add': { class: 'on-request' },
103
+ 'local-setup remove': { class: 'on-request' },
95
104
  'skill list': { class: 'read' },
96
105
  'skill recommend': { class: 'read' },
97
106
  'skill bind': { class: 'on-request' },
@@ -104,6 +113,8 @@ export const COMMAND_CLASS = {
104
113
  'epic new': { class: 'local-write', flags: { issue: 'on-request' } },
105
114
  'foundation new': { class: 'local-write' },
106
115
  'foundation status': { class: 'read' },
116
+ // E174: creates items on the platform; `--dry-run` only reads.
117
+ 'foundation publish': { class: 'on-request' },
107
118
  status: { class: 'read' },
108
119
  next: { class: 'read' },
109
120
  // Skipping, deferring or clearing a blocker is a decision about the work: the person's.
@@ -173,6 +184,20 @@ export const COMMAND_CLASS = {
173
184
  'worktree list': { class: 'read' },
174
185
  'worktree remove': { class: 'local-write' },
175
186
  standup: { class: 'read' },
187
+ // E181: `yad map` starts a local server and runs until Ctrl-C (as `brain view` does); --html writes one file into
188
+ // the local reports folder — or `--html <file>`, ANY path named, replacing a plain file there — and --fetch
189
+ // downloads. Local only, so local-write; never on the read allow list, so the prompt still covers the path.
190
+ map: { class: 'local-write' },
191
+ // E180: the local reports folder. `list` reads; `open` starts the browser; `prune` alone is a dry run, and
192
+ // `prune --apply` deletes saved reports, so only when the person asks.
193
+ 'reports list': { class: 'read' },
194
+ 'reports open': { class: 'local-write' },
195
+ 'reports prune': { class: 'read', flags: { apply: 'on-request' } },
196
+ // E184: `brand` and `brand check` read; `brand init` writes the Product's committed brand file (and `--force`
197
+ // replaces the team's edits), so only when the person asks — as `toolbox add` and `skill bind` (review 1).
198
+ 'brand show': { class: 'read' },
199
+ 'brand check': { class: 'read' },
200
+ 'brand init': { class: 'on-request' },
176
201
  'issues list': { class: 'read' },
177
202
  // Adds labels on the team's repos: asked for, never a side effect.
178
203
  'issues labels': { class: 'on-request' },
@@ -202,6 +227,18 @@ export const COMMAND_CLASS = {
202
227
  'history list': { class: 'read' },
203
228
  'history show': { class: 'read' },
204
229
  'history search': { class: 'read' },
230
+ // E176: runs Graphify in each code repo and writes only the brain's own ignored folder (and a local
231
+ // .git/info/exclude line). The two reads print names taken from the code, which anyone can write.
232
+ 'brain build': { class: 'local-write' },
233
+ 'brain query': { class: 'read' },
234
+ 'brain status': { class: 'read' },
235
+ // E179: the focused questions the planning and building skills ask before they plan or edit.
236
+ 'brain file': { class: 'read' },
237
+ 'brain story': { class: 'read' },
238
+ // E177: starts a local server (127.0.0.1, a one-time key), or with --html writes one file — the brain's own
239
+ // ignored folder, or any path named. Local only, so local-write; never pre-approved (a prefix rule would let
240
+ // `--html <file>` overwrite any file, as `standup --out` could).
241
+ 'brain view': { class: 'local-write' },
205
242
  'repo list': { class: 'read' },
206
243
  'repo refresh': { class: 'local-write', flags: { push: 'default-push', 'allow-branch': 'on-request' } },
207
244
  'repo sync': { class: 'local-write' },
@@ -236,7 +273,8 @@ const stronger = (a, b) => (STRENGTH.indexOf(b) > STRENGTH.indexOf(a) ? b : a);
236
273
  // A test holds this to bin/yad.mjs.
237
274
  export const DEFAULT_ACTION = {
238
275
  skill: 'list', history: 'list', repo: 'list', 'risk-map': 'check', codeowners: 'check', docs: 'list',
239
- toolbox: 'list', member: 'list', issues: 'list', worktree: 'list', signing: 'check', ci: 'check',
276
+ toolbox: 'list', member: 'list', issues: 'list', worktree: 'list', signing: 'check', ci: 'check', brain: 'status',
277
+ reports: 'list', 'local-setup': 'list', brand: 'show',
240
278
  };
241
279
 
242
280
  // The entry for a command line's words: `<cmd> <action>` when it has one, else `<cmd>` (or its default action).
@@ -300,7 +338,8 @@ export const RULES = [
300
338
  { id: 'update', text: 'When the guide says the install is behind yadflow, run `yad update --open-pr --json` without asking: it commits the update on its own branch in each repo and opens a PR/MR, which a person merges. Show the person every row that has a `hint` (a repo held back, refused, or left half done) with its `reason`, wait for them, then run it again. Never use `yad update --push` unless the person asks for it.' },
301
339
  { id: 'pushes', text: 'Commit, push your own branch, and open a review PR/MR without asking. Open a task PR/MR without asking only when `yad dial open-pr` is `auto`; otherwise ask first. Ask every time, right before anything that pushes straight to the default branch: say what it will push (the branch and the commits), and wait for a yes given then. A request made earlier, or "don\'t ask", is not that yes. Never force-push.' },
302
340
  { id: 'on-request', text: 'Run a command the guide classes `on-request` only when the person asked for that exact change or gave you what it records: `yad dial … --to`, `yad mode solo|team`, `yad kill`, `yad unkill`, `yad skip`, `yad defer`, `yad unblock`, `yad setup`/`new`/`init` (with the answers the person gave to the questions the guide lists), `yad skill bind`, `yad toolbox add`, `yad toolbox connect --verify` (after the yes the connect-tool rule asks for), a flag that passes a guard (`--force`, `--overwrite-local`, `--allow-branch`), and the others the guide marks.' },
303
- { id: 'connect-tool', text: 'Offer to connect a tool when yad hands you its `connect` command (a toolbox finding in `yad setup`, `check` or `update`, a `yad doctor` hint, or a design preflight) or a skill says to: one tool, one question — ask once per tool in a run, whichever offer comes first, and never again after a no. To connect a tool (install it on this machine and record it as the team\'s choice), run `yad toolbox connect <tool> --json` first and show the person its `ask` word for word. Ask once; go on only on a yes. Then run exactly its `agent` steps, in order, with no other source, version or flag; hand over its `person` steps with their `why`, and wait for them. Then run the `verify` command it gave (`--replace` is in it only when the question said what it replaces). If a step fails, stop and show the person its output; never try another way to install it. A new MCP server is loaded when the agent starts: if `verify` passed but your session does not see the server (in Claude Code, `/mcp`), tell the person to restart the agent and run the step again (for a design or testing tool, its connect skill with `action: refresh` and the same `tool` first); never record the tool as unavailable for that. The `claude` steps are Claude Code\'s: with another agent, hand every step to the person.' },
341
+ { id: 'connect-tool', text: 'Offer to connect a tool when yad hands you its `connect` command (a toolbox finding in `yad setup`, `check` or `update`, a `yad doctor` hint, or a design preflight) or a skill says to: one tool, one question — ask once per tool in a run, whichever offer comes first, and never again after a no. To connect a tool (install it on this machine and record it as the team\'s choice), run `yad toolbox connect <tool> --json` first and show the person its `ask` word for word. Ask once; go on only on a yes. Then run exactly its `agent` steps, in order, with no other source, version or flag; hand over its `person` steps with their `why`, and wait for them. Then run the `verify` command it gave (`--replace` is in it only when the question said what it replaces). If a step fails, stop and show the person its output; never try another way to install it. A new MCP server is loaded when the agent starts: if `verify` passed but your session does not see the server (in Claude Code, `/mcp`), tell the person to restart the agent and run the step again (for a design or testing tool, its connect skill with `action: refresh` and the same `tool` first); never record the tool as unavailable for that. A step that names `claude` or `claude-code` is Claude Code\'s: with another agent, hand every step to the person.' },
342
+ { id: 'local-setup', text: 'When yad says local setup steps are waiting for this machine (`yad setup`, `update`, `check`, `join`, `doctor`, or the guide\'s `upkeep`), run `yad local-setup list --json`. Go through the steps whose `state` is `pending` or `ask`, one at a time: tell the person its `title`, its `purpose`, its `impact` (what it changes for them), whether its `when` is `required` or `optional`, and show its `commands` word for word (and, for a team step, its `check.run`). When its `source` is `team`, or `vetted` is false, say "written by your team, not vetted by yadflow" (or "not what this yadflow writes" when `known` is false). The person decides each step. Run nothing a step names (its `commands`, `verify` or `check.run`) before their yes to that step; a `person: true` step is theirs to run (a login, a key): hand it to them with its commands, and wait until they say it is done. After the yes, run the `commands` of a step that is not `person: true`; then (for a person step, once they say it is done) run its `verify` command, and `yad local-setup done <id>`. On a no, run `yad local-setup skip <id> --reason "<their words>"`. For a step whose `state` is `ok` and `recorded` is false, run `yad local-setup done <id>` without asking. When `yad setup` or `update` says your team has no steps of its own yet (or the person asks), look for what a member\'s machine needs for this project that the list does not cover (a `.env.example` to copy, `docker-compose.yml`, the Node version in `.nvmrc`, a `make setup`, the README\'s setup section) and propose each as a step: its title, purpose, impact, `required` or `optional`, and its commands word for word, and say that a step they accept is committed and offered to every member\'s agent. Never put a secret value in a step: name where it comes from (an environment variable, the team\'s vault). Add only the steps the person says yes to: write each to a file outside the repo and run `yad local-setup add --from <file>`; `.sdlc/local-setup.json` and `LOCAL-SETUP.md` then go in a commit like any other change. Never edit those two files by hand: `add` and `remove` change the team\'s steps.' },
304
343
  { id: 'build-halts', text: 'A Build step the yad-run skill halted (`blocked`: a failing check, a scope overrun, a contract touch) waits for the person: never move it on (`yad build step … in_progress`) until they say it is resolved.' },
305
344
  { id: 'never-by-hand', text: 'Never hand-write `.sdlc/` files, approvals, or text between yad markers; only `yad` commands and the yad-* skills change them.' },
306
345
  { id: 'record-truly', text: 'When you record Build work you did yourself, say so: `yad build step … --via auto` and `yad build trust … --ran-by machine`, as the yad-run skill does. The defaults record a person\'s work.' },
@@ -381,7 +420,9 @@ export const claudeBlock = () => ['@AGENTS.md'];
381
420
  // command that is not a read (`yad mode` begins `yad mode team`). Written into `.claude/settings.json`
382
421
  // `permissions.allow` as `Bash(yad <words>:*)`; nothing that writes, pushes, posts or approves is ever there.
383
422
  // `standup` reads, but `--out <file>` writes the file named: a prefix rule would let it overwrite any file.
384
- const NOT_PREAPPROVED = new Set(['standup', 'issues list', 'issues show']);
423
+ // `brain query`, `brain status`, `brain file` and `brain story` print names read from the code (E176, E179), which
424
+ // anyone can write, as `issues show` does.
425
+ const NOT_PREAPPROVED = new Set(['standup', 'issues list', 'issues show', 'brain query', 'brain status', 'brain file', 'brain story']);
385
426
  export function readAllowList() {
386
427
  const keys = Object.keys(COMMAND_CLASS);
387
428
  const reads = keys.filter((key) => {
@@ -408,6 +449,21 @@ export const SHIPPED_ALLOW_LISTS = Object.freeze([
408
449
  'gate status', 'gate review', 'gate walkthrough', 'review context', 'review chat', 'review cards', 'review walkthrough', 'member list',
409
450
  'worktree list', 'claims', 'owners', 'history list', 'history show', 'history search', 'repo list', 'risk-map check', 'codeowners check', 'story frames', 'docs list',
410
451
  'thread', 'reconcile check'].map((k) => `Bash(yad ${k}:*)`),
452
+ // next release (E180): `reports list`
453
+ ['guide', 'help', 'doctor', 'detect', 'signing check', 'ci check', 'toolbox list', 'toolbox check', 'skill list', 'skill recommend', 'foundation status', 'status', 'next',
454
+ 'gate status', 'gate review', 'gate walkthrough', 'review context', 'review chat', 'review cards', 'review walkthrough', 'member list',
455
+ 'worktree list', 'reports list', 'claims', 'owners', 'history list', 'history show', 'history search', 'repo list', 'risk-map check', 'codeowners check', 'story frames', 'docs list',
456
+ 'thread', 'reconcile check'].map((k) => `Bash(yad ${k}:*)`),
457
+ // next release (E185): `local-setup list`
458
+ ['guide', 'help', 'doctor', 'detect', 'signing check', 'ci check', 'toolbox list', 'toolbox check', 'local-setup list', 'skill list', 'skill recommend', 'foundation status', 'status', 'next',
459
+ 'gate status', 'gate review', 'gate walkthrough', 'review context', 'review chat', 'review cards', 'review walkthrough', 'member list',
460
+ 'worktree list', 'reports list', 'claims', 'owners', 'history list', 'history show', 'history search', 'repo list', 'risk-map check', 'codeowners check', 'story frames', 'docs list',
461
+ 'thread', 'reconcile check'].map((k) => `Bash(yad ${k}:*)`),
462
+ // next release (E184, #553): `brand show`, `brand check`
463
+ ['guide', 'help', 'doctor', 'detect', 'signing check', 'ci check', 'toolbox list', 'toolbox check', 'local-setup list', 'skill list', 'skill recommend', 'foundation status', 'status', 'next',
464
+ 'gate status', 'gate review', 'gate walkthrough', 'review context', 'review chat', 'review cards', 'review walkthrough', 'member list',
465
+ 'worktree list', 'reports list', 'brand show', 'brand check', 'claims', 'owners', 'history list', 'history show', 'history search', 'repo list', 'risk-map check', 'codeowners check', 'story frames', 'docs list',
466
+ 'thread', 'reconcile check'].map((k) => `Bash(yad ${k}:*)`),
411
467
  ].map((list) => Object.freeze(list)));
412
468
 
413
469
  // Entries an older yadflow pre-approved that this one does not (a command later reclassed as a write, say).
@@ -1,7 +1,7 @@
1
1
  // The flags `yad` reads a value after (`--dir <path>`), and those it reads a list of (`--approver a --approver b`).
2
2
  // Shared by the parser in bin/yad.mjs and the agent guard (cli/agent-guard.mjs), which must read a command line
3
3
  // the way yad does: `yad --dir ../product gate approve …` is still `gate approve`. `-m` takes a value too.
4
- export const VALUE_FLAGS = new Set(['--dir', '--issue', '--body-file', '--priority', '--status', '--assignee', '--date', '--sort', '--closed-since', '--type', '--message', '--task', '--ai', '--risk', '--repo', '--platform', '--base', '--title', '--scope', '--branch', '--pr', '--epic', '--team', '--body', '--out', '--since', '--until', '--member', '--format', '--reason', '--profile', '--parent', '--inherits', '--to', '--retro-ship', '--merge-commit', '--path', '--ide-targets', '--theme', '--thread', '--by', '--count', '--engagement', '--keep', '--role', '--fallback', '--detect', '--install', '--source', '--tz', '--verdict', '--ran-by', '--note', '--uid', '--run', '--via', '--kind', '--confirm',
4
+ export const VALUE_FLAGS = new Set(['--dir', '--issue', '--body-file', '--priority', '--status', '--assignee', '--date', '--sort', '--closed-since', '--type', '--message', '--task', '--ai', '--risk', '--repo', '--platform', '--base', '--title', '--scope', '--branch', '--pr', '--epic', '--team', '--body', '--out', '--since', '--until', '--member', '--format', '--reason', '--profile', '--parent', '--inherits', '--to', '--retro-ship', '--merge-commit', '--path', '--ide-targets', '--theme', '--thread', '--by', '--count', '--engagement', '--keep', '--role', '--fallback', '--detect', '--install', '--source', '--tz', '--verdict', '--ran-by', '--note', '--uid', '--run', '--via', '--kind', '--confirm', '--limit', '--older-than', '--from', '--logo', '--mark',
5
5
  // E159: the setup answers an agent passes after asking the person.
6
6
  '--default-branch', '--design', '--design-url', '--testing', '--testing-url', '--learning', '--connect', '--coderabbit']);
7
- export const LIST_FLAGS = new Set(['--signal', '--approver', '--add-repo']);
7
+ export const LIST_FLAGS = new Set(['--signal', '--approver', '--add-repo', '--label', '--add', '--remove']);
@@ -0,0 +1,21 @@
1
+ The MIT License (MIT)
2
+
3
+ Copyright (c) 2017-2021 Guillaume Plique (Yomguithereal)
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
13
+ all 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
21
+ THE SOFTWARE.
@@ -0,0 +1,21 @@
1
+ The MIT License (MIT)
2
+
3
+ Copyright (c) 2016-2021 Guillaume Plique (Yomguithereal)
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
13
+ all 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
21
+ THE SOFTWARE.
@@ -0,0 +1,12 @@
1
+ Copyright (C) 2013-2025, Alexis Jacomy, Guillaume Plique, Benoît Simard https://www.sigmajs.org
2
+
3
+ Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"),
4
+ to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense,
5
+ 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:
6
+
7
+ The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
8
+
9
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
10
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
11
+ 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
12
+ IN THE SOFTWARE.