cskwork / scopeweaver

# ScopeWeaver
An LLM multi-agent autonomous penetration-testing system (Go backend + Next.js frontend)
English · 한국어
---
> **About this project.** ScopeWeaver is a derivative of Autumn-27/ARTEX,
> rebranded and translated into English and Korean. It is built from upstream commit `160fe13`.
Modification date: **2026-10-02**. See provenance and changes; this is not a release tag.
Verification status and known limitations.
> The code and architecture originate in ARTEX. This standalone derivative changes the product
> name, English/Korean interface and messages, documentation, and distribution targets. See Provenance and changes
> for the full list of what differs from upstream, and License and disclaimer
> for the terms, which are unchanged (AGPL-3.0).
>
> **Authorization.** This is a security-testing tool. Use it only against systems you own or are
> explicitly authorized to test. The upstream usage restrictions still apply — read them below.
---
## Language
English is the default. Select English, Korean or Simplified Chinese (`zh-Hans`) in the interface.
Bare `zh`, `zh-CN` and `zh-SG` resolve to Simplified Chinese; explicit Hans tags keep their script even
with a Traditional region. Undeclared Traditional tags (`zh-Hant`, `zh-TW`, `zh-HK`, `zh-MO`) fall
through to the next preference rather than select Simplified Chinese. See the
contributor locale guide. The server's durable default is
`language` in system settings; `SCOPEWEAVER_LANGUAGE` (or `ARTEX_LANGUAGE`) supplies the environment
fallback. Operating-system `LANG` does not select the application language.
Requests prefer `lang`, then supported `Accept-Language` preferences, then the `scopeweaver_locale`
cookie, then the server default. New HTTP-created tasks retain their language across queues and
restarts; older tasks without saved language use the server default. Built-in agent guidance and
output instructions use the run language; user-edited templates and stored evidence remain intact.
Report/CSV/ZIP labels use the export request's language. Full documentation and
Korean references include the bundled skill guidance.
Standalone penetration-testing conversations save confirmed findings directly to the Findings
page under the unassigned-task group. Each conversation keeps its own finding history across
turns without starting a task. Missing or invalid prompts for Auto, Penetration testing, Report
writer, and Finding retest fall back to their role defaults; render failures appear in backend logs.
## Screenshots
These captures show ScopeWeaver's English interface with the included fictional demo data.
They do not represent scans of live targets. See the Korean screenshots
and mobile view.
| Dashboard | Tasks |
| :---: | :---: |
| | |
| Findings | Settings |
| | |
Original Chinese screenshots remain in the screenshots directory, credited to
upstream ARTEX.
---
## Approval records
The global "Approval records" view, the in-task "Interception approval" panel, and the approval
cards shown inside