kanteam-linux-arm64 1.47.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +335 -0
- package/backlog +0 -0
- package/package.json +11 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2025 Backlog.md
|
|
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.
|
package/README.md
ADDED
|
@@ -0,0 +1,335 @@
|
|
|
1
|
+
<h1 align="center">Kanteam</h1>
|
|
2
|
+
<p align="center">Markdown‑native multi-user, self-hostable Kanban & backlog manager for any Git repository</p>
|
|
3
|
+
|
|
4
|
+
<p align="center">
|
|
5
|
+
<code>npm i -g kanteam</code> or <code>bun add -g kanteam</code>
|
|
6
|
+
</p>
|
|
7
|
+
|
|
8
|
+
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
> **Kanteam is a friendly fork of [Backlog.md](https://backlog.md) by [Alex Gavrilescu (MrLesk)](https://github.com/MrLesk), released under the MIT License.**
|
|
13
|
+
> It stays **drop-in compatible** with existing Backlog.md projects — same `backlog/` data directory, same `config.yml`, and the `backlog` command still works — and adds features aimed at **teams self-hosting a shared instance**. All credit for the original tool goes upstream; see [NOTICE](NOTICE). Kanteam is an independent fork, not affiliated with or endorsed by the Backlog.md project.
|
|
14
|
+
|
|
15
|
+
### What Kanteam adds on top of Backlog.md
|
|
16
|
+
|
|
17
|
+
| Addition | What it does |
|
|
18
|
+
| --- | --- |
|
|
19
|
+
| 🔄 **Remote auto-sync** | optional `autoPull` before each operation and `autoPush` after each commit (CLI, web, MCP) |
|
|
20
|
+
| 👥 **Per-user commit attribution** | web/MCP commits attributed to the authenticated user (e.g. behind an oauth2-proxy) for real multi-user hosting |
|
|
21
|
+
| 🌐 **Streamable HTTP MCP transport** | run the MCP server over HTTP with per-request commit attribution |
|
|
22
|
+
| 📎 **Attachment serving** | task attachments served over `/attachments` so images actually load in the web viewer |
|
|
23
|
+
| 🖼️ **Image lightbox** | click-to-zoom on Markdown images |
|
|
24
|
+
| ↩️ **Hard line breaks** | single newlines render as line breaks in the web viewer |
|
|
25
|
+
|
|
26
|
+
Home: [kanteam.com](https://kanteam.com) · Everything below documents the shared Backlog.md core.
|
|
27
|
+
|
|
28
|
+
|
|
29
|
+
---
|
|
30
|
+
|
|
31
|
+
> **Backlog.md** turns any folder with a Git repo into a **self‑contained project board**
|
|
32
|
+
> powered by plain Markdown files and a zero‑config CLI.
|
|
33
|
+
> Built for **spec‑driven AI development** — structure your tasks so AI agents deliver predictable results.
|
|
34
|
+
|
|
35
|
+
## Features
|
|
36
|
+
|
|
37
|
+
* 📝 **Markdown-native tasks** -- manage every issue as a plain `.md` file
|
|
38
|
+
|
|
39
|
+
* 🤖 **AI-Ready** -- Works with Claude Code, Gemini CLI, Codex, Kiro & any other MCP or CLI compatible AI assistants
|
|
40
|
+
|
|
41
|
+
* 📊 **Instant terminal Kanban** -- `backlog board` paints a live board in your shell
|
|
42
|
+
|
|
43
|
+
* 🌐 **Modern web interface** -- `backlog browser` launches a sleek web UI for visual task management
|
|
44
|
+
|
|
45
|
+
* 🔍 **Powerful search** -- fuzzy search across tasks, docs & decisions with `backlog search`
|
|
46
|
+
|
|
47
|
+
* 📋 **Rich query commands** -- view, list, filter, or archive tasks with ease
|
|
48
|
+
* ✅ **Definition of Done defaults** -- add a reusable checklist to every new task
|
|
49
|
+
|
|
50
|
+
* 📤 **Board export** -- `backlog board export` creates shareable markdown reports
|
|
51
|
+
|
|
52
|
+
* 🔒 **100 % private & offline** -- backlog lives entirely inside your repo and you can manage everything locally
|
|
53
|
+
|
|
54
|
+
* 💻 **Cross-platform** -- runs on macOS, Linux, and Windows
|
|
55
|
+
|
|
56
|
+
* 🆓 **MIT-licensed & open-source** -- free for personal or commercial use
|
|
57
|
+
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
## <img src="./.github/5-minute-tour-256.png" alt="Getting started" width="28" height="28" align="center"> Getting started
|
|
62
|
+
|
|
63
|
+
```bash
|
|
64
|
+
# Install
|
|
65
|
+
bun i -g kanteam
|
|
66
|
+
# or: npm i -g kanteam
|
|
67
|
+
|
|
68
|
+
# Initialize in any Git repo
|
|
69
|
+
backlog init "My Awesome Project"
|
|
70
|
+
|
|
71
|
+
# Or initialize without Git for local/non-code projects
|
|
72
|
+
backlog init "Personal Planning" --no-git
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
The init wizard will ask how you want to connect AI tools:
|
|
76
|
+
- **CLI instructions** (recommended) — creates a short instruction file that tells agents to run `backlog instructions overview`.
|
|
77
|
+
- **MCP connector** — optionally auto-configures Claude Code, Codex, Gemini CLI, Kiro or Cursor for teams that prefer MCP.
|
|
78
|
+
- **Skip** — no AI setup; use Backlog.md purely as a task manager.
|
|
79
|
+
|
|
80
|
+
Backlog data is stored in a project-local backlog folder such as `backlog/`, `.backlog/`, or a custom project-relative path configured through `backlog.config.yml`. Tasks remain human-readable Markdown files (e.g. `task-10 - Add core search functionality.md`). Git is optional: `backlog init --no-git` creates a filesystem-only project and disables cross-branch checks, remote operations, and auto-commit.
|
|
81
|
+
|
|
82
|
+
---
|
|
83
|
+
|
|
84
|
+
### Working with AI agents
|
|
85
|
+
|
|
86
|
+
This is the recommended flow for Claude Code, Codex, Gemini CLI, Kiro and similar tools — following the **spec‑driven AI development** approach.
|
|
87
|
+
After running `backlog init`, agents should start by running `backlog instructions overview`. Work in this loop:
|
|
88
|
+
|
|
89
|
+
**Step 1 — Describe your idea.** Tell the agent what you want to build and ask it to split the work into small tasks with clear descriptions and acceptance criteria.
|
|
90
|
+
|
|
91
|
+
**🤖 Ask your AI Agent:**
|
|
92
|
+
> I want to add a search feature to the web view that searches tasks, docs, and decisions. Please decompose this into small Backlog.md tasks.
|
|
93
|
+
|
|
94
|
+
> [!NOTE]
|
|
95
|
+
> **Review checkpoint #1** — read the task descriptions and acceptance criteria.
|
|
96
|
+
|
|
97
|
+
**Step 2 — One task at a time.** Work on a single task per agent session, one PR per task. Good task splitting means each session can work independently without conflicts. Make sure each task is small enough to complete in a single conversation. You want to avoid running out of context window.
|
|
98
|
+
|
|
99
|
+
**Step 3 — Plan before coding.** Ask the agent to research and write an implementation plan in the task. Do this right before implementation so the plan reflects the current state of the codebase.
|
|
100
|
+
|
|
101
|
+
**🤖 Ask your AI Agent:**
|
|
102
|
+
> Work on BACK-10 only. Research the codebase and write an implementation plan in the task. Wait for my approval before coding.
|
|
103
|
+
|
|
104
|
+
> [!NOTE]
|
|
105
|
+
> **Review checkpoint #2** — read the plan. Does the approach make sense? Approve it or ask the agent to revise.
|
|
106
|
+
|
|
107
|
+
**Step 4 — Implement and verify.** Let the agent implement the task.
|
|
108
|
+
|
|
109
|
+
> [!NOTE]
|
|
110
|
+
> **Review checkpoint #3** — review the code, run tests, check linting, and verify the results match your expectations.
|
|
111
|
+
|
|
112
|
+
If the output is not good enough: clear the plan/notes/final summary, refine the task description and acceptance criteria, and run the task again in a fresh session.
|
|
113
|
+
|
|
114
|
+
---
|
|
115
|
+
|
|
116
|
+
### Working without AI agents
|
|
117
|
+
|
|
118
|
+
Use Backlog.md as a standalone task manager from the terminal or browser.
|
|
119
|
+
|
|
120
|
+
```bash
|
|
121
|
+
# Create and refine tasks
|
|
122
|
+
backlog task create "Render markdown as kanban"
|
|
123
|
+
backlog task edit BACK-1 -d "Detailed context" --ac "Clear acceptance criteria"
|
|
124
|
+
|
|
125
|
+
# Track work
|
|
126
|
+
backlog task list -s "To Do"
|
|
127
|
+
backlog task edit BACK-1 --comment "Can we split the UI work into a separate PR?" --comment-author @sara
|
|
128
|
+
backlog search "kanban"
|
|
129
|
+
backlog board
|
|
130
|
+
|
|
131
|
+
# Work visually in the browser
|
|
132
|
+
backlog browser
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
You can switch between AI-assisted and manual workflows at any time — both operate on the same Markdown task files. It is recommended to modify tasks via Backlog.md commands (CLI/MCP/Web) rather than editing task files manually, so field types and metadata stay consistent. Tasks can record project-root-relative modified files and later be found with `backlog search --modified-file src/path.ts --plain`. Use task comments for discussion and review notes; comment bodies may contain Markdown, but standalone `---` lines are reserved as comment delimiters. Use Implementation Notes for execution progress and Final Summary for completion notes.
|
|
136
|
+
|
|
137
|
+
**Learn more:** [CLI reference](CLI-INSTRUCTIONS.md) | [Advanced configuration](ADVANCED-CONFIG.md)
|
|
138
|
+
|
|
139
|
+
---
|
|
140
|
+
|
|
141
|
+
## <img src="./.github/web-interface-256.png" alt="Web Interface" width="28" height="28" align="center"> Web Interface
|
|
142
|
+
|
|
143
|
+
Launch a modern, responsive web interface for visual task management:
|
|
144
|
+
|
|
145
|
+
```bash
|
|
146
|
+
# Start the web server (opens browser automatically)
|
|
147
|
+
backlog browser
|
|
148
|
+
|
|
149
|
+
# Custom port
|
|
150
|
+
backlog browser --port 8080
|
|
151
|
+
|
|
152
|
+
# Don't open browser automatically
|
|
153
|
+
backlog browser --no-open
|
|
154
|
+
```
|
|
155
|
+
|
|
156
|
+
**Features:**
|
|
157
|
+
- Interactive Kanban board with drag-and-drop
|
|
158
|
+
- Task creation and editing with rich forms
|
|
159
|
+
- Interactive acceptance criteria editor with checklists
|
|
160
|
+
- Real-time updates across all views
|
|
161
|
+
- Responsive design for desktop and mobile
|
|
162
|
+
- Task archiving with confirmation dialogs
|
|
163
|
+
- Seamless CLI integration - all changes sync with markdown files
|
|
164
|
+
|
|
165
|
+
|
|
166
|
+
|
|
167
|
+
To keep the Web UI running as an auto-starting local service, see [Running Backlog.md as a Service](backlog/docs/doc-003%20-%20Running-Backlog-Browser-as-a-Service.md).
|
|
168
|
+
|
|
169
|
+
---
|
|
170
|
+
|
|
171
|
+
## 🔧 MCP Integration (Model Context Protocol)
|
|
172
|
+
|
|
173
|
+
CLI instructions are the default AI setup. MCP remains supported for AI coding assistants like Claude Code, Codex, Gemini CLI and Kiro when you explicitly prefer an MCP connector.
|
|
174
|
+
You can run `backlog init` (even if you already initialized Backlog.md) and choose MCP integration, or follow the manual steps below.
|
|
175
|
+
|
|
176
|
+
### Transports: stdio (default) and Streamable HTTP
|
|
177
|
+
|
|
178
|
+
`backlog mcp start` serves over **stdio** by default — one process per local client.
|
|
179
|
+
|
|
180
|
+
For a **shared, hosted** MCP server (a single long-lived process for a team), use the
|
|
181
|
+
Streamable HTTP transport:
|
|
182
|
+
|
|
183
|
+
```bash
|
|
184
|
+
backlog mcp start --http --port 6421 --host 127.0.0.1
|
|
185
|
+
```
|
|
186
|
+
|
|
187
|
+
Run it **behind an authenticating reverse proxy** (e.g. oauth2-proxy). When the proxy
|
|
188
|
+
forwards the end-user identity headers and `commit_author_from_proxy_headers` is enabled,
|
|
189
|
+
each request's commit is attributed to that user (committer stays the server identity) —
|
|
190
|
+
the same model as the web UI. The transport is stateless, so no per-client process is
|
|
191
|
+
spawned.
|
|
192
|
+
|
|
193
|
+
See **[Authenticated multi-user hosting](AUTHENTICATED-HOSTING.md)** for an end-to-end
|
|
194
|
+
setup (Keycloak + oauth2-proxy, web + MCP, and the two MCP client auth options).
|
|
195
|
+
|
|
196
|
+
### Client guides
|
|
197
|
+
|
|
198
|
+
<details>
|
|
199
|
+
<summary><strong>Claude Code</strong></summary>
|
|
200
|
+
|
|
201
|
+
```bash
|
|
202
|
+
claude mcp add backlog --scope user -- backlog mcp start
|
|
203
|
+
```
|
|
204
|
+
|
|
205
|
+
</details>
|
|
206
|
+
|
|
207
|
+
<details>
|
|
208
|
+
<summary><strong>Codex</strong></summary>
|
|
209
|
+
|
|
210
|
+
```bash
|
|
211
|
+
codex mcp add backlog -- backlog mcp start
|
|
212
|
+
```
|
|
213
|
+
|
|
214
|
+
</details>
|
|
215
|
+
|
|
216
|
+
<details>
|
|
217
|
+
<summary><strong>Gemini CLI</strong></summary>
|
|
218
|
+
|
|
219
|
+
```bash
|
|
220
|
+
gemini mcp add backlog -s user backlog mcp start
|
|
221
|
+
```
|
|
222
|
+
|
|
223
|
+
</details>
|
|
224
|
+
|
|
225
|
+
<details>
|
|
226
|
+
<summary><strong>Kiro</strong></summary>
|
|
227
|
+
|
|
228
|
+
```bash
|
|
229
|
+
kiro-cli mcp add --scope global --name backlog --command backlog --args mcp,start
|
|
230
|
+
```
|
|
231
|
+
|
|
232
|
+
</details>
|
|
233
|
+
|
|
234
|
+
Use the shared `backlog` server name everywhere. The server finds the active project from your client's MCP roots, and re-resolves when you switch workspace or worktree. Until it finds one, it serves `backlog://init-required`. A single user-scope server covers every repo.
|
|
235
|
+
|
|
236
|
+
### Manual config
|
|
237
|
+
|
|
238
|
+
```json
|
|
239
|
+
{
|
|
240
|
+
"mcpServers": {
|
|
241
|
+
"backlog": {
|
|
242
|
+
"command": "backlog",
|
|
243
|
+
"args": ["mcp", "start"],
|
|
244
|
+
"env": {
|
|
245
|
+
"BACKLOG_CWD": "/absolute/path/to/your/project"
|
|
246
|
+
}
|
|
247
|
+
}
|
|
248
|
+
}
|
|
249
|
+
}
|
|
250
|
+
```
|
|
251
|
+
|
|
252
|
+
Set `BACKLOG_CWD` to pin the server to one project and stop workspace following. Use it to always target the same backlog, or when your client can't report MCP roots.
|
|
253
|
+
If your IDE supports custom args but not env vars, you can also use `["mcp", "start", "--cwd", "/absolute/path/to/your/project"]`.
|
|
254
|
+
|
|
255
|
+
> [!IMPORTANT]
|
|
256
|
+
> When adding the MCP server manually, add a short instruction to your CLAUDE.md/AGENTS.md files telling agents to read `backlog://workflow/overview`.
|
|
257
|
+
> This step is not required when using `backlog init` as it adds these instructions automatically.
|
|
258
|
+
> For CLI-based setups, use `backlog instructions overview` to fetch the current workflow guidance.
|
|
259
|
+
|
|
260
|
+
|
|
261
|
+
Once connected, agents can read the Backlog.md workflow instructions via `backlog://workflow/overview`, with detailed guides at `backlog://workflow/task-creation`, `backlog://workflow/task-execution`, and `backlog://workflow/task-finalization`.
|
|
262
|
+
Use `/mcp` command in your AI tool (Claude Code, Codex, Kiro) to verify if the connection is working.
|
|
263
|
+
|
|
264
|
+
---
|
|
265
|
+
|
|
266
|
+
## <img src="./.github/cli-reference-256.png" alt="CLI Reference" width="28" height="28" align="center"> CLI reference
|
|
267
|
+
|
|
268
|
+
Full command reference — task management, search, board, docs, decisions, and more: **[CLI-INSTRUCTIONS.md](CLI-INSTRUCTIONS.md)**
|
|
269
|
+
|
|
270
|
+
Quick examples: `backlog`, `backlog instructions`, `backlog task create`, `backlog task list`, `backlog task edit`, `backlog milestone add`, `backlog milestone rename`, `backlog milestone remove`, `backlog search`, `backlog board`, `backlog browser`.
|
|
271
|
+
|
|
272
|
+
Full help: `backlog --help`
|
|
273
|
+
|
|
274
|
+
---
|
|
275
|
+
|
|
276
|
+
## <img src="./.github/configuration-256.png" alt="Configuration" width="28" height="28" align="center"> Configuration
|
|
277
|
+
|
|
278
|
+
Backlog.md merges the following layers (highest → lowest):
|
|
279
|
+
|
|
280
|
+
1. CLI flags
|
|
281
|
+
2. Project config file:
|
|
282
|
+
- `backlog.config.yml` when present
|
|
283
|
+
- otherwise `backlog/config.yml` or `.backlog/config.yml`
|
|
284
|
+
3. Built‑ins
|
|
285
|
+
|
|
286
|
+
### Interactive wizard (`backlog config`)
|
|
287
|
+
|
|
288
|
+
Run `backlog config` with no arguments to launch the full interactive wizard. This is the same experience triggered from `backlog init` when you opt into advanced settings, and it walks through the complete configuration surface:
|
|
289
|
+
- Cross-branch accuracy: `checkActiveBranches`, `remoteOperations`, and `activeBranchDays`.
|
|
290
|
+
- Git workflow: `autoCommit`, `autoPull` (run `git pull --rebase` before each operation so reads/writes use the latest), `autoPush` (run `git push` after every commit so changes are shared immediately) — both work from the CLI, web UI and MCP — and `bypassGitHooks`.
|
|
291
|
+
- Hosted/web attribution: `commitAuthorFromProxyHeaders` (opt-in, default off) — the web server sets each commit's **author** from the identity forwarded by an auth proxy; the committer stays the server identity. Header names are configurable via `proxyAuthorEmailHeader` (default `x-forwarded-email`) and `proxyAuthorNameHeader` (default `x-forwarded-preferred-username`), matching oauth2-proxy. Only enable behind a proxy you control.
|
|
292
|
+
- ID formatting: enable or size `zeroPaddedIds`.
|
|
293
|
+
- Editor integration: pick a `defaultEditor` with availability checks.
|
|
294
|
+
- Definition of Done defaults: interactively add/remove/reorder/clear project-level `definition_of_done` checklist items.
|
|
295
|
+
- Web UI defaults: choose `defaultPort` and whether `autoOpenBrowser` should run.
|
|
296
|
+
|
|
297
|
+
Skipping the wizard (answering "No" during init) applies the safe defaults that ship with Backlog.md:
|
|
298
|
+
- `checkActiveBranches=true`, `remoteOperations=true`, `activeBranchDays=30`.
|
|
299
|
+
- `autoCommit=false`, `autoPull=false`, `autoPush=false`, `bypassGitHooks=false`.
|
|
300
|
+
- `zeroPaddedIds` disabled.
|
|
301
|
+
- `defaultEditor` unset (falls back to your environment).
|
|
302
|
+
- `defaultPort=6420`, `autoOpenBrowser=true`.
|
|
303
|
+
|
|
304
|
+
For filesystem-only projects, run `backlog init --no-git`. Backlog.md will not run `git init`, and the saved config forces `checkActiveBranches=false`, `remoteOperations=false`, and `autoCommit=false` so CLI, Web, and MCP local-file workflows do not depend on a Git repository.
|
|
305
|
+
|
|
306
|
+
Whenever you revisit `backlog init` or rerun `backlog config`, the wizard pre-populates prompts with your current values so you can adjust only what changed.
|
|
307
|
+
|
|
308
|
+
### Definition of Done defaults
|
|
309
|
+
|
|
310
|
+
Set project-wide DoD items with `backlog config` (or during `backlog init` advanced setup), in the Web UI (Settings → Definition of Done Defaults), or by editing the project config file directly:
|
|
311
|
+
|
|
312
|
+
```yaml
|
|
313
|
+
definition_of_done:
|
|
314
|
+
- Tests pass
|
|
315
|
+
- Documentation updated
|
|
316
|
+
- No regressions introduced
|
|
317
|
+
```
|
|
318
|
+
|
|
319
|
+
When a project uses root config discovery, edit `backlog.config.yml` instead of `backlog/config.yml`.
|
|
320
|
+
|
|
321
|
+
These items are added to every new task by default. You can add more on create with `--dod`, or disable defaults per task with `--no-dod-defaults`.
|
|
322
|
+
|
|
323
|
+
For the full configuration reference (all options, commands, and detailed notes), see **[ADVANCED-CONFIG.md](ADVANCED-CONFIG.md)**.
|
|
324
|
+
|
|
325
|
+
---
|
|
326
|
+
|
|
327
|
+
## 🌐 Community Tools
|
|
328
|
+
|
|
329
|
+
- **[vscode-backlog-md](https://marketplace.visualstudio.com/items?itemName=ysamlan.vscode-backlog-md)** - VS Code extension with issues panel, kanban view, and editing. ([ysamlan/vscode-backlog-md](https://github.com/ysamlan/vscode-backlog-md))
|
|
330
|
+
|
|
331
|
+
---
|
|
332
|
+
|
|
333
|
+
### License
|
|
334
|
+
|
|
335
|
+
Kanteam, like its upstream **Backlog.md** (© Alex Gavrilescu / MrLesk), is released under the **MIT License** – do anything, just give credit. See [LICENSE](LICENSE) and [NOTICE](NOTICE).
|
package/backlog
ADDED
|
Binary file
|
package/package.json
ADDED