Skip to content
Back to search

https://github.com/Autumn-27/ScopeSentry

通过 ScopeSentry MCP 管理安全扫描平台(项目、任务、模板、资产、节点)。在用户提到 ScopeSentry、MCP、API Key、扫描任务、资产查询时使用。

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Autumn-27/ScopeSentry with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Autumn-27/ScopeSentry'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/autumn-27--scopesentry/badge.svg)](/listings/autumn-27--scopesentry)

HTML

<a href="/listings/autumn-27--scopesentry"><img src="/api/listings/autumn-27--scopesentry/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

git clone https://github.com/Autumn-27/ScopeSentry.git
cd ScopeSentry
# Change the MongoDB and Redis account passwords in the. env file.
docker-compose -f single-host-deployment.yml up -d

After running, there will be four containers: mongodb, redis, scope-sentry (server), and scopesentry-scan (scan). By default, there will be one scanning node.

View the initial user password and the secondary verification password of the plug-in

```docker logs scope-sentry```

**Add new nodes(Optional)**

git clone https://github.com/Autumn-27/ScopeSentry-Scan.git
cd ScopeSentry-Scan/build

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 366 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. ## name: scopesentry-mcp
  3. description: 通过 ScopeSentry MCP 管理安全扫描平台(项目、任务、模板、资产、节点)。在用户提到 ScopeSentry、MCP、API Key、扫描任务、资产查询时使用。
  4. # ScopeSentry MCP 使用指南
  5. 面向**已部署 ScopeSentry 实例**的用户。通过 Cursor(或其他 MCP 客户端)连接平台,无需本地源码。
  6. ## 1. 准备工作
  7. ### 1.1 确认服务可访问
  8. - 默认 Web 界面:`http://<主机>`
  9. - MCP 端点:`http://<主机>/mcp`(若前面有反向代理或前端代理,以实际 `/mcp` 地址为准)
  10. ### 1.2 创建 API Key
  11. 1. 浏览器登录 ScopeSentry Web 界面
  12. 2. 进入 **API Key** 管理页创建密钥(或通过管理员提供的接口创建)
  13. 3. 保存返回的 `ssk_...` 字符串(**仅显示一次**)
  14. ### 1.3 配置 Cursor MCP
  15. Cursor → Settings → MCP → 添加服务器:
  16. ```json
  17. {
  18. "mcpServers": {
  19. "scopesentry": {
  20. "url": "http://<你的主机>:8082/mcp",
  21. "headers": {
  22. "X-API-Key": "ssk_你的密钥"
  23. }
  24. }
  25. }
  26. }
  27. ```
  28. 也可使用:`Authorization: Bearer ssk_你的密钥`
  29. 配置完成后重启 MCP 或重载 Cursor,确认工具列表中出现 `list_projects`、`list_assets` 等。
  30. ---
  31. ## 2. 工具一览
  32. | 工具 | 用途 |
  33. | ---------------------- | ----------------- |
  34. | `list_projects` | 按标签分组的项目树(含项目 ID) |
  35. | `list_projects_data` | 分页项目列表,可按名称搜索 |
  36. | `get_project` | 项目详情 |
  37. | `create_project` | 新建项目;同名且范围有效时替换资产范围 |
  38. | `list_tasks` | 扫描任务列表 |
  39. | `get_task` | 任务详情 |
  40. | `list_scan_templates` | 扫描模板列表 |
  41. | `get_scan_template` | 模板详情 |
  42. | `list_plugin_modules` | 扫描流水线模块名 |
  43. | `list_plugins` | 可用插件(含 hash、默认参数) |
  44. | `create_scan_template` | 创建扫描模板 |
  45. | `create_scan_task` | 创建扫描任务 |
  46. | `list_assets` | 查询各类资产(分页列表) |
  47. | `count_assets` | 统计资产数量(`/api/assets/common/total`) |
  48. | `get_asset_detail` | 资产或漏洞详情 |
  49. | `add_asset_tag` | 为资产添加标签 |
  50. | `list_nodes` | 扫描节点列表 |
  51. 各工具参数以 MCP 工具描述(schema)为准;`list_assets` / `count_assets` 的 search、filter 语法一致,查询资产前可先阅读 `list_assets` description。
  52. 需要知道「共多少条」时用 `count_assets`(对应 Web 分页总数接口),不必为了数总数反复翻页 `list_assets`。
  53. ---
  54. ## 3. 常用工作流
  55. ### 3.1 按项目查资产
  56. 当用户或上下文**已有项目条件**时,优先带上 `filter.project` 缩小范围,避免跨项目数据过多导致响应变慢。若无明确项目,可不强制加项目筛选。
  57. 1. `list_projects` 或 `list_projects_data` 获取目标项目的 **ObjectID**(`id` / `children[].value`)
  58. 2. `list_assets` 传入 `filter.project`(**必须是 ID,不能写项目中文名**)
  59. ```json
  60. {
  61. "asset_type": "asset",
  62. "pageIndex": 1,
  63. "pageSize": 20,
  64. "search": "domain=^example.com",
  65. "filter": {
  66. "project": ["<项目ObjectID>"]
  67. }
  68. }
  69. ```
  70. ### 3.2 创建扫描任务
  71. 1. `list_nodes` 获取在线节点名称
  72. 2. `list_scan_templates` 或 `create_scan_template` 获取模板 **ObjectID**
  73. 3. `create_scan_task`:`name`、`node` 必填,`template` 填模板 ID(不能填模板名)
  74. **目标来源 `targetSource`(与 Web 端一致):**
  75. | targetSource | 说明 | 必填参数 |
  76. | --- | --- | --- |
  77. | `general` | 直接输入目标 | `target` |
  78. | `project` | 从项目读取目标 | `project`(项目 ObjectID 数组) |
  79. | `asset` | 从 Web 资产库搜索 | `search`;可选 `project`、`filter`、`targetNumber` |
  80. | `RootDomain` | 从根域名库搜索 | `search`;可选 `project`、`filter`、`targetNumber` |
  81. | `subdomain` | 从子域名库搜索 | `search`;可选 `project`、`filter`、`targetNumber` |
  82. | `UrlScan` | 从 URL 扫描结果搜索 | `search`;可选 `project`、`filter`、`targetNumber` |
  83. | `*Source`(如 `subdomainSource`) | 从资产页「选中/搜索」创建 | `targetTp=search` 时用 `search`;`targetTp=select` 时用 `targetIds` |
  84. **示例 — 直接扫根域名:**
  85. ```json
  86. {
  87. "name": "example-子域名收集",
  88. "node": ["node-1"],
  89. "template": "<模板ObjectID>",
  90. "targetSource": "general",
  91. "target": "example.com\nfoo.com",
  92. "project": ["<项目ObjectID>"]
  93. }
  94. ```
  95. **示例 — 从子域名库续扫(按上一任务名筛选):**
  96. ```json
  97. {
  98. "name": "example-端口与漏洞",
  99. "node": ["node-1"],
  100. "template": "<后续模块模板ObjectID>",
  101. "targetSource": "subdomain",
  102. "search": "task==\"example-子域名收集\"",
  103. "project": ["<项目ObjectID>"]
  104. }
  105. ```
  106. ### 3.3 根域名完整信息收集(推荐两阶段)
  107. 当输入为**根域名**且要进行**完整信息收集**时,建议分两次扫描,不要一次跑全流水线。
  108. **原因:** 分布式任务以**单个目标**为单位分发。根域名作为目标时,某节点分到该根域名后,在该节点上扫出的子域名也会继续在该节点执行后续模块,容易造成负载不均、速度慢、易出错。
  109. **最佳实践:**
  110. 1. **第一阶段 — 仅子域名收集**
  111. - `targetSource`: `general`
  112. - `target`: 所有根域名(多行)
  113. - 模板:仅启用 `SubdomainScan`、`SubdomainSecurity`(子域名扫描 + 子域名接管)
  114. - 用 `get_task` 等待任务完成
  115. 2. **第二阶段 — 后续模块**
  116. - `targetSource`: `subdomain`
  117. - `search`: `task=="<第一阶段任务名称>"`(精确匹配任务名)
  118. - 可选 `project` 缩小范围
  119. - 模板:端口扫描、资产测绘、漏洞扫描等(可不含 SubdomainScan)
  120. - 子域名作为独立目标分发到各节点,并行效率更高
  121. 也可在 Web 界面「子域名」资产页按任务名筛选后,使用「从子域名创建任务」,效果相同。
  122. ```mermaid
  123. flowchart LR
  124. A[根域名列表] --> B[阶段1: general + SubdomainScan]
  125. B --> C[子域名入库]
  126. C --> D[阶段2: subdomain + task==阶段1任务名]
  127. D --> E[端口/资产/漏洞等模块]
  128. ```
  129. ### 3.4 创建扫描模板
  130. 1. `list_plugin_modules` → 模块名列表
  131. 2. `list_plugins`(可按 `module` 过滤)→ 各插件 `hash` 与默认 `parameter`
  132. 3. `create_scan_template`:用 `modules` 指定「模块 → 插件 hash 数组」
  133. ---
  134. ## 4. 资产查询(`list_assets` / `count_assets`)
  135. `count_assets` 与 `list_assets` 使用相同的 `asset_type`、`search`、`filter`,返回 `{ "total": N }`,对应 Web 端 `/api/assets/common/total`。
  136. ```json
  137. {
  138. "asset_type": "subdomain",
  139. "search": "task==\"某任务名\"",
  140. "filter": {"project": ["<项目ObjectID>"]}
  141. }
  142. ```
  143. **性能建议(`list_assets` / `count_assets` 通用):** 有项目条件时优先用 `filter.project` 缩小范围;`search` 中对已建索引字段尽量用 `==` 全等或 `^` 前缀匹配(见 [4.3](#43-search-搜索表达式)),避免大面积 `=` 模糊查询拖慢响应。无项目上下文时不强制加项目筛选。
  144. 支持 `filter.project` 的类型见 [4.4](#44-filter-精确过滤) 表格。
  145. ### 4.1 资产类型 `asset_type`
  146. `asset`、`RootDomain`、`subdomain`、`app`、`mp`、`UrlScan`、`SensitiveResult`、`DirScanResult`、`crawler`、`vulnerability`、`PageMonitoring`、`IPAsset`、`SubdomainTakerResult`
  147. 别名示例:`web`→asset、`vuln`→vulnerability、`ip`→IPAsset、`url`→UrlScan
  148. ### 4.2 参数说明
  149. | 参数 | 说明 |
  150. | ------------------------ | --------------------------------------- |
  151. | `pageIndex` / `pageSize` | 分页,默认 1 / 20 |
  152. | `search` | 搜索表达式(见下节) |
  153. | `filter` | 精确过滤 JSON(见下节) |
  154. | `sort` | 仅 UrlScan、DirScanResult 支持按 `length` 排序 |
  155. | `sid` | 仅 SensitiveResult:敏感规则名称 |
  156. `search` 与 `filter` **可同时使用**。
  157. ### 4.3 search 搜索表达式
  158. 自定义 DSL(**不是 SQL**):
  159. | 运算符 | 含义 | 索引 | 示例 |
  160. | ---- | ---- | ---- | --------------------------- |
  161. | `=` | 模糊匹配(regex) | 不走索引 | `domain=example` |
  162. | `==` | 精确匹配(全等) | **走索引** | `port==443` |
  163. | `!=` | 排除 | — | `port!="80"` |
  164. | `&&` | 与 | — | `domain==example.com && port==443` |
  165. | `||` | 或 | — | `title=admin || body=login` |
  166. **索引与运算符:** `domain`、`ip`、`port`、`title` 等字段已建索引,但仅 **`==` 全等** 或 **值以 `^` 开头的前缀匹配**(如 `domain=^example.com`)能走索引;**`=` 会转为 regex 模糊匹配,无法使用索引**,数据量大时易变慢。
  167. **所有类型通用 search 字段:** `tag`、`task`(任务名称)、`rootDomain`
  168. **project 不能写在 search 里**(无效或与 `&&` 组合时报错)。筛项目请用 `filter.project`。
  169. **各类型常用 search 字段:**
  170. | asset_type | 字段 |
  171. | -------------------- | ----------------------------------------------------------------------------------- |
  172. | asset | domain, ip, port, service, app, title, statuscode, icon, banner, type, body, header |
  173. | RootDomain | domain, icp, company |
  174. | subdomain | domain, ip, type, value |
  175. | app | name, icp, company, category, description, url, apk |
  176. | mp | name, icp, company, category, description, url |
  177. | UrlScan | url, input, source, resultId, type |
  178. | SensitiveResult | url, sname, body, info, md5 |
  179. | DirScanResult | url, statuscode, redirect, length |
  180. | vulnerability | url, vulname, matched, request, response, level |
  181. | crawler | url, method, body, resultId |
  182. | PageMonitoring | url, hash, diff, response |
  183. | IPAsset | ip, domain, port, service, webServer, app |
  184. | SubdomainTakerResult | domain, value, type, response |
  185. **search 示例:**
  186. - `domain==www.example.com && port==443`(全等,走索引)
  187. - `domain=^example.com`(前缀匹配,走索引)
  188. - `ip==192.168.1.1`
  189. - `task=="某任务名"`
  190. - `level==high`(vulnerability)
  191. - `statuscode==200`(DirScanResult)
  192. 需模糊包含时再用 `=`,如 `title=admin`(不走索引,宜配合项目等条件缩小范围)。
  193. ### 4.4 filter 精确过滤
  194. JSON 对象:同 key 多个值为 **OR**,不同 key 为 **AND**。
  195. **有项目条件时优先用 `project`:** 若用户或上下文已明确项目,且 asset_type 支持 `project`,应带上以缩小范围;无项目信息时不强制。
  196. | filter key | 含义 | 取值说明 |
  197. | ------------ | -------- | -------------------------------------------------------- |
  198. | `project` | 所属项目 | **ObjectID**,用 `list_projects` / `list_projects_data` 获取 |
  199. | `task` | 来源任务 | **任务名称**,用 `list_tasks` 的 `name` |
  200. | `port` | 端口 | 如 `"443"` |
  201. | `service` | 服务/协议 | 如 `"https"` |
  202. | `app` | 应用指纹 | 如 `"Nginx"` |
  203. | `icon` | 图标 hash | |
  204. | `statuscode` | HTTP 状态码 | 主要用于 asset |
  205. | `status` | 状态 | UrlScan/DirScan HTTP 码;漏洞/敏感信息处理状态 |
  206. | `level` | 漏洞等级 | critical / high / medium / low / info |
  207. | `type` | 类型 | 如子域名记录类型 A、CNAME |
  208. | `color` | 敏感规则颜色 | SensitiveResult |
  209. | `sname` | 敏感规则名 | SensitiveResult |
  210. | `tags` | 标签 | |
  211. **各类型可用 filter key:**
  212. | asset_type | filter key |
  213. | ------------------------------------- | --------------------------------------------------------------- |
  214. | asset | project, port, service, app, icon, statuscode, type, task, tags |
  215. | RootDomain | project, tags |
  216. | subdomain | project, type, task, tags |
  217. | app / mp | project, tags |
  218. | UrlScan | status, tags |
  219. | DirScanResult | status, tags |
  220. | SensitiveResult | status, color, sname, tags |
  221. | crawler | project, task, tags |
  222. | vulnerability | project, level, status, task, tags |
  223. | PageMonitoring / SubdomainTakerResult | tags |
  224. | IPAsset | project, port, service, app |
  225. **filter 示例:**
  226. ```json
  227. {"project": ["<项目ObjectID>"], "port": ["443"]}
  228. ```
  229. **组合查询示例:**
  230. ```json
  231. {
  232. "asset_type": "asset",
  233. "search": "domain=^baidu && port==443",
  234. "filter": {"project": ["<项目ObjectID>"]},
  235. "pageIndex": 1,
  236. "pageSize": 10
  237. }
  238. ```
  239. **注意:**
  240. - 有项目条件时优先带 `filter.project`(支持时);无项目上下文可不强制
  241. - `filter.project` 勿填项目显示名称
  242. - 已知值用 `==`,前缀用 `^`;避免对大表滥用 `=` 模糊匹配
  243. - UrlScan 的 HTTP 状态用 `filter.status`;DirScanResult 可在 search 中用 `statuscode==200`
  244. - SensitiveResult 按规则名:`search` 用 `sname=规则名`,或 `filter.sname`
  245. ### 4.5 排序 sort
  246. 仅 **UrlScan**、**DirScanResult** 支持:
  247. ```json
  248. {"length": "ascending"}
  249. ```
  250. 其他类型忽略 `sort`,按时间默认排序。
  251. ---
  252. ## 5. 扫描模板模块名
  253. `TargetHandler`、`SubdomainScan`、`SubdomainSecurity`、`PortScanPreparation`、`PortScan`、`PortFingerprint`、`AssetMapping`、`AssetHandle`、`URLScan`、`WebCrawler`、`URLSecurity`、`DirScan`、`VulnerabilityScan`、`PassiveScan`
  254. ---
  255. ## 6. 故障排查
  256. | 现象 | 处理 |
  257. | --------- | -------------------------------------------------- |
  258. | MCP 无工具 | 检查 URL、API Key、ScopeSentry 是否运行 |
  259. | 401 / 403 | 重新创建或更换 API Key |
  260. | 资产查不到 | 确认 `filter.project` 为 ObjectID;勿在 search 写 project |
  261. | 模板/任务创建失败 | `template` 必须是模板 ObjectID;`node` 填在线节点名 |
  262. | 查询很慢/卡住 | 有项目时加 `filter.project`;search 对已索引字段改用 `==` 或 `^` 前缀,少用 `=`;缩小 `pageSize` |
  263. ---
README.md · README · 181 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align=center>
  2. <img src="docs/images/favicon.ico"/>
  3. </div>
  4. English | [中文](./README_CN.md)
  5. [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/Autumn-27/ScopeSentry-Scan)
  6. ## Introduction
  7. Scope Sentry is a tool with functions such as asset mapping, subdomain enumeration, information leakage detection, vulnerability scanning, directory scanning, subdomain takeover, crawler, and page monitoring. By building multiple nodes, users can freely choose nodes to run scanning tasks. When new vulnerabilities emerge, it can quickly check whether the concerned assets have related components.
  8. Distributed Implementation Reference Articles: [https://mp.weixin.qq.com/s/xfgRxUjljoQ8KzacblktxA](https://mp.weixin.qq.com/s/xfgRxUjljoQ8KzacblktxA)
  9. Server Recommendation: [lightnode](https://www.lightnode.com/?inviteCode=CQ11JU&promoteWay=LINK)
  10. ## Discord:
  11. [https://discord.gg/GWVwSBBm48](https://discord.gg/GWVwSBBm48)
  12. ## Language
  13. Server:python - FastApi
  14. Scan:go
  15. Front-end:vue - vue-element-plus-admin
  16. ## Website
  17. - Official Website: [https://www.scope-sentry.top](https://www.scope-sentry.top/en/)
  18. - Github: [https://github.com/Autumn-27/ScopeSentry](https://github.com/Autumn-27/ScopeSentry)
  19. - Scanner source code: [https://github.com/Autumn-27/ScopeSentry-Scan](https://github.com/Autumn-27/ScopeSentry-Scan)
  20. - UI source code: [https://github.com/Autumn-27/ScopeSentry-UI](https://github.com/Autumn-27/ScopeSentry-UI)
  21. - Plugin Market: [Plugin Market](https://plugin.scope-sentry.top/en)
  22. - Plugin Template:[https://github.com/Autumn-27/ScopeSentry-Plugin-Template](https://github.com/Autumn-27/ScopeSentry-Plugin-Template)
  23. ## Install
  24. ```
  25. git clone https://github.com/Autumn-27/ScopeSentry.git
  26. cd ScopeSentry
  27. # Change the MongoDB and Redis account passwords in the. env file.
  28. docker-compose -f single-host-deployment.yml up -d
  29. ```
  30. After running, there will be four containers: mongodb, redis, scope-sentry (server), and scopesentry-scan (scan). By default, there will be one scanning node.
  31. View the initial user password and the secondary verification password of the plug-in
  32. ```docker logs scope-sentry```
  33. **Add new nodes(Optional)**
  34. ```
  35. git clone https://github.com/Autumn-27/ScopeSentry-Scan.git
  36. cd ScopeSentry-Scan/build
  37. # Edit the connection information for MongoDB and Redis in the .env file. NodeName is the node name, and each node name should be unique (if it is empty, it will be randomly generated, and you can change the name in the web interface).
  38. docker-compose -f scan-docker-compose.yml up -d
  39. ```
  40. ## Plugin Flowchart
  41. <img src="流程图.svg"/>
  42. ## Current Features
  43. - Plugin System (Add any tool through extension)
  44. - Subdomain Enumeration
  45. - Subdomain Takeover Detection
  46. - Port Scanning
  47. - Asset Identification
  48. - Directory Scanning
  49. - Vulnerability Scanning
  50. - Sensitive Information Leakage Detection
  51. - URL Extraction
  52. - Crawler
  53. - Page Monitoring
  54. - Custom WEB Fingerprint
  55. - POC Import
  56. - Asset Grouping
  57. - Multi-Node Scanning
  58. - Webhook
  59. ## To Do
  60. - Weak Password Cracking
  61. -
  62. ## Installation
  63. For installation instructions, see the [official website](https://www.scope-sentry.top)
  64. ## Communication
  65. Discord:
  66. [https://discord.gg/agsYdAyN](https://discord.gg/agsYdAyN)
  67. ## Screenshots
  68. ### Login
  69. ![alt text](docs/images/login.png)
  70. ### Homepage Dashboard
  71. ![alt text](docs/images/index-en.png)
  72. ## Plugin System
  73. ![alt text](docs/images/plugin-cn.png)
  74. ![alt text](docs/images/plugin-m-en.png)
  75. ## Asset Data
  76. ### Assets
  77. ![alt text](docs/images/asset-en.png)
  78. ![alt text](docs/images/asset-s-en.png)
  79. ![alt text](docs/images/asset-s2-en.png)
  80. ### Quick syntax search:
  81. ![alt text](docs/images/search.gif)
  82. ## Root Domain
  83. ![alt text](docs/images/rootdomain-cn.png)
  84. ### Subdomains
  85. ![alt text](docs/images/subdomain-en.png)
  86. ### Subdomain Takeover
  87. ![alt text](docs/images/subt-en.png)
  88. ### APP
  89. ![alt text](docs/images/app-cn.png)
  90. ### 小程序
  91. ![alt text](docs/images/mp-cn.png)
  92. ### URL
  93. ![alt text](docs/images/craw-cn.png)
  94. ### Crawler
  95. ![alt text](docs/images/craw-en.png)
  96. ### Sensitive Information
  97. ![alt text](docs/images/sns-cn.png)
  98. ### Directory Scanning
  99. ![alt text](docs/images/dir-cn.png)
  100. ### Vulnerabilities
  101. ![alt text](docs/images/vul-en.png)
  102. ### Page Monitoring
  103. ![alt text](docs/images/page-en.png)
  104. ![alt text](docs/images/page-change.png)
  105. ## Projects
  106. ![](docs/images/project-cn.png)
  107. ## Project asset aggregation
  108. ### Panel - Overview
  109. ![](docs/images/project-dsh.png)
  110. ### Subdomains
  111. ![](docs/images/project-subdomain.png)
  112. ### Port
  113. ![](docs/images/project-port.png)
  114. ### Service
  115. ![](docs/images/project-server.png)
  116. ## Tasks
  117. ![](docs/images/create-task-en.png)
  118. ## Task Progress
  119. ![](docs/images/task-pg-en.png)
  120. ## Nodes
  121. ![](docs/images/node-cn.png)
  122. #License
  123. All branches of this project follow AGPL-3.0, and additional terms need to be followed:
  124. 1. The commercial use of this software requires a separate commercial license.
  125. 2. Companies, organizations, and for-profit entities must obtain a commercial license before using, distributing, or modifying this software.
  126. Individuals and non-profit organizations are free to use this software in accordance with the terms of AGPL-3.0.
  127. 4. If you have any commercial license inquiries, please contact rainy-autumn@outlook.com .

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.