Repository navigation
Releases
APTv1.1.7
Changes
- Version labels come from the installed package instead of a hardcoded string. The sidebar, the footer, the general settings page and the
installed-versionelement render the version the workbench actually runs, and the update page falls back to the installed version when the version check has not returned one. - Read-only demo deployments can mark the document with
data-demo-read-only="true". In that mode the workspace switcher is hidden, switching spaces and changing the password stay disabled, and the demo banner uses the shared theme tokens. - Deleting a task or a plan from the storage workspace uses the solid red danger style, and disabled upload controls follow the selected light or dark theme.
- The public read-only demo and its synthetic data are documented in the README and the i18n READMEs.
Verification
-
npm run build,npm run test:distribution,node tests/i18n.mjs(23 scenarios, 63 view renders) andnode tests/static-assets.mjspass in both editions. -
python -X utf8 scripts/check-doc-translations.py(16941 assertions community, 16244 personal) andpython -X utf8 tests/doc-translation-format.pypass with no errors. -
The served HTML no longer contains the
__AP_INSTALLED_VERSION__placeholder, and the read-only demo rejects task execution, password changes and the personal workspace. -
Docker version tag
johncoke/agenticpentest:v1.1.7(alsolatest) -
Image index digest
sha256:aa1a116ad150644f25b145567e405d594e2b987cc91fc32c80f951e9558f2504 -
Source revision
f6a7af95940deb0bb581ee985efb06dc56db2dda
APTv1.1.6
Changes
- Platform updates recreate the container with the security options it already runs under: a custom seccomp profile,
systempaths=unconfinedand an AppArmor profile survive the update instead of failing withRuntime setting changed: SecurityOpt. - Compose-managed deployments write an inline seccomp profile into the deployment backup directory and reference that file, because Compose only accepts a profile path.
- Standalone Docker recreations reuse the container's
CapDropandSecurityOptvalues; a container without security options is recreated without them.
Verification
-
python3 tests/platform-updater.py(15 tests) andpython3 tests/deploy-security-opt.py(3 tests) pass on Linux in both editions. -
A live Compose deployment whose container carries an inline seccomp profile and
apparmor=agenticpentest-bwrapwas recreated with byte-identicalHostConfig.SecurityOpt. -
Docker version tag
johncoke/agenticpentest:v1.1.6(alsolatest) -
Image index digest
sha256:7b2205e256174688a53f3da1fef545965d909976b4ee7c5dca3d80b43bd512af -
Source revision
64930fdb1263c5357d9df4a72cc7047db5391a08
This release supersedes the short-lived v1.1.5 build, whose Compose path could not materialize an inline seccomp profile. The v1.1.4 images remain available at their original digests.
APTv1.1.4
Changes
- The Agent workflow canvas shows the saved input source, targets, source samples and the number of existing findings.
- Project workflows execute
tool,threat,pocandreportnodes with checkpoints, so an interrupted run resumes without replaying finished nodes. - Web checks resolve bare domains and IP addresses; explicit ports and paths are preserved, certificate errors never downgrade to HTTP, and redirects are not followed.
- The update settings page and usage guidance were revised.
Verification
-
CI build and distribution checks pass, together with
tests/web-target.mjs,tests/http-target-input.mjsandtests/project-node-api.mjsin both editions. -
Images are built for linux/amd64 and linux/arm64, smoke-tested on both platforms, and deployed to a Linux host for health and data-preservation checks.
-
Docker version tag
johncoke/agenticpentest:v1.1.4(alsolatest) -
Image index digest
sha256:ea2a98c8275cace61a1a0218a2b5bdaf6e26d365e9bde09de220eb51cfe67a71 -
Source revision
cd469fab85e23b7896c893f9e2f74c8dfbf00b96
The v1.1.3 images remain available at their original digests.
APTv1.1.3
Changes
- Web checks that require a full HTTP(S) URL now reject incomplete or malformed input with a clear validation message. Valid URLs keep their supplied protocol.
- Task details and review summaries display the same localized message for new and historical URL errors. Validation performs no network requests.
- GitHub Release titles now follow the
APTv1.x.xnaming convention.
Verification
Both editions passed offline input regression and browser checks of the error message in all seven supported languages. The images passed health and source checks on Linux amd64 and arm64.
- Docker version tag
johncoke/agenticpentest:v1.1.3 - Image index digest
sha256:a2399f889949b1183c7a0181683545f4d331eeaa63887777245ae0428bb1dd86
APTv1.1.2
What's changed
- View saved finding evidence in the Burp Suite desktop extension using a workspace-scoped
burp:readcredential. The viewer displays the stored origin, request method, and status code and sends no requests to the target. - Keep editor syntax highlighting and the language label synchronized when the selected language changes. Preserve the editor buffer and undo history.
- Recover the MCP bridge after a dropped upstream session or local address change. Tool calls that may have reached the prior session are not replayed.
Burp extension installation and setup
Container image
- Version tag
johncoke/agenticpentest:v1.1.2 - Platforms
linux/amd64andlinux/arm64 - Index digest
sha256:544c7c96af36aaa0571dd4b8f6093dedf11f1fcf6d0fba4e639837beb5225684
Both platforms passed image health and source-identity smoke tests. The feature regression used synthetic evidence and loopback fixtures. See #54, #55, #56 and #57.
APTv1.1.1
v1.1.1 brings durable Agent-to-Leader handoffs, a customizable directed workflow canvas and independent security assessment / security testing entry points.
- Canvas: draft/publish snapshots, node colors and directed ports, branch connections, disconnect/undo, mouse pan/zoom, workflow history and examples.
- Agent collaboration: bounded evidence reviews, retained negative evidence and checkpoints, explicit incomplete states and model budgets.
- Independent assessment/testing forms: direct domain/IP asset association, automatic classification and clearer domain entry.
- UI: larger prompt editor, anchored model menus, localized controls and themed updater/threat-model actions.
- MCP: deployment preservation ignores only usage clocks (
users.lastSeen,developer_grants.lastUsedAt); credential fields and business data remain checked. MCP Verified retained.
Validation: both actual editions passed isolated clean install/build, default regression, MCP HTTP/stdio/OAuth/reconnect/revocation, edition-feature parity and distribution checks. PR CI passed. Fixtures use disposable databases, loopback services and synthetic model replies; this does not measure field false-positive rates or token savings.
Known limitations: project workflows can process saved evidence through input/filter/review/summary nodes. Other project node types currently report unsupported-node; dependents skip and independent supported branches continue. Selecting a published workflow does not mean every node has a target executor. The separate general canvas task runner has its own capability bindings. Same-job execution is sequential. Cloud SDKs must be installed for cloud execution. IP proxy pool remains planned for v1.2.
Upgrade: back up the database with its matching master key and runtime configuration. Keep existing ports, environment, data and tool volumes. Do not use down -v. See README upgrade instructions.
Community-only: contextual guidance in the lower-right corner follows the current page and language.
Verified image: johncoke/agenticpentest:v1.1.1 (linux/amd64 and linux/arm64).
Immutable multi-platform digest: sha256:4f2303d2417d0f0ece45745c147dcbdb519b8aa89a0475eeb91cae157ff8bdf2.
Merged source: 6dc551baae01f6f51fcf252207b34fa49b7813e8.
APTv1.1.0
v1.1 connects scanner evidence, LLM retesting, threat modeling and PoC/Exploit drafts in one workflow. Package and immutable release tag: 1.1.0 / v1.1.0.
- Scan result import is a dedicated navigation entry with designed uploads and vendor SVGs. Nuclei JSONL, Nessus XML, Greenbone XML, Qualys SCAN XML/strict CSV and Rapid7 XML Export 2.0; up to 20 files, 50,000,000 bytes and 1,000 observations per file.
- Batch processing reduces per-finding steps. Parsing uses no model calls; compact evidence, bounded budgets and durable checkpoints reuse completed work. Existing checker evidence remains authoritative; generated PoC/Exploit code is saved as drafts.
- Threat analysis separates per-batch timeout from round budget, repairs scoped asset references and continues after partial architecture adoption without regenerating completed batches.
- Shared controls improve floating labels, icon alignment, compact checkboxes and model binding across seven languages and both themes.
- MCP portability adds validated LAN origins, exact Bonjour/Avahi hostnames and bounded stdio name-resolution fallback. OAuth bindings, permissions, expiry and revocation remain enforced. Local listener processes use
shell:false; updater-key purpose, permissions and revocation are documented. MCP Verified is retained in the community README.
Validation
Both actual edition checkouts passed isolated build, full regression, MCP and edition-feature checks. Scanner UI coverage spans seven languages, two themes and 1440/768/390px widths. Export acceptance passed with 11 supported samples / 196 observations, plus two expected unsupported-format rejections. See the attached validation manifest for pinned hashes and available version evidence.
Final images passed both architecture smoke checks, source/static-asset identity checks and isolated data-preserving upgrade/rollback tests. Existing deployment checks verified preserved database records, keys, configuration and rollback images, served assets/entry pages, OAuth discovery and authenticated read-only desktop MCP reconnection. No external sample targets or real LLM calls were used for acceptance.
Images and source
- Source:
7c94ff385d3b76efe5937d71f8b3cfc4ac3d6cf0 - Image:
docker.io/johncoke/agenticpentest:v1.1.0 - Platforms:
linux/amd64,linux/arm64 - Immutable index digest:
sha256:caa41558a3f115471cf5a474d28b1678fc162de1c297fd0222391d16d40058d3 latestand the source SHA alias were checked against that same digest. The attached release manifest records architecture-specific digests.
Upgrade and limits
Back up the database with its matching master key, configuration and updater registration. Retain data/tool volumes, installation identity and model/Agent settings; do not use down -v. Keep a healthy rollback image and matching backup. Upgrade guide.
Compatibility covers the documented export profiles, not every scanner version or custom template. Unsupported/unmapped checks remain inconclusive. .local recovery requires multicast reachability; simulations cover address changes and process restarts, but physical network switching was not tested. The IP proxy pool is scheduled for v1.1.1.
Supported formats and limits · Detailed release scope
Known deployment limitation: an active MCP client can update developer_grants.lastUsedAt during a managed upgrade and trigger a false preservation rollback. This deployment used an audited host-only normalization of that timestamp, preserving all credential and business fields; the shared fix is tracked in #44 for v1.1.1. Pause desktop MCP clients during an upgrade if this occurs. Native browser .local resolution remains environment-dependent; bridge resolution passed, and the affected browser entry was verified via LAN IP.
APTv1.0.4
v1.0.4 — Background tool installation and platform updates
This maintenance release builds on v1.0.3 and adds deployment-aware updates from System settings → Version updates.
- Run maintained-tool installations in the background. A download tray shows progress and logs; navigation and browser refresh restore the same account/workspace's jobs.
- Detect the runtime OS and CPU architecture, replace incompatible binaries or virtual environments on reinstall, and automatically check maintained tools after installation. Missing dependencies and execution requirements are shown separately from download completion.
- Resolve newly installed built-in tools while preserving custom executable overrides. Fix missing-static-file responses and improve update-check feedback.
- Update the workbench through a restricted, host-registered SSH channel. The web container receives neither the Docker socket nor host root access.
- Require the actual team administrator's current password and confirmation. Block upgrades during active work, preserve configuration/data, display persistent progress and logs, restart, verify health, and roll back failed deployments with their matching data backup.
- Pull Docker images by full source revision and pin the verified digest. Linux Compose and standalone Docker on Linux/macOS are supported; managed source upgrades require Linux/systemd and a clean official Git checkout.
- Fall back to public HTTPS Git metadata when the GitHub API is unavailable. Public repository checks need no token or GitHub SSH key; configured metadata proxies are supported, including Docker Desktop's host alias. Image downloads use the Docker daemon's registry/proxy configuration.
- Update all seven UI languages and README upgrade instructions. Preserve authorization notices, deployment identity and the existing network-scope rules.
First upgrade and setup
Installations without this feature, including v1.0.1, need one manual upgrade to this v1.0.4 build. Back up the database with its matching encryption key and configuration. Reuse existing data/tool volumes, ports and runtime settings; never run docker compose down -v.
After upgrading, run the one-time host registration described in the platform update guide. Then use System settings → Version updates → Check for updates → Update platform.
Native Windows source deployments, Codespaces, foreground processes and archive-only source directories retain manual upgrade instructions. Arbitrary imported tools still require explicit availability checks; a download does not supply every runtime or execution permission.
Verification
- Actions published and smoke-tested Linux amd64 and arm64 images with
v1.0.4,latest, and full/short source-SHA tags. - Actual browser-driven upgrades passed on Ubuntu Docker (both distributions) and Apple Silicon Docker, including restart, retained sessions and preserved synthetic data.
- Isolated Linux/systemd source upgrades and failed source/Docker migrations rolled back successfully.
- Administrator access, maintenance gates, stale-response handling, seven-language UI and documentation checks passed.
中文
v1.0.4 在 v1.0.3 的基础上补充工具后台安装、系统/架构识别、安装后自动检测,以及真正的系统设置内平台更新。
首次从 v1.0.1 等旧版升级,仍需先手动安装本次 v1.0.4,再由宿主机管理员按指南一次性注册更新通道。之后可在 系统设置 → 版本更新 → 检查更新 → 更新平台 中输入管理员当前密码并确认执行。
支持 Linux/macOS 上的 Docker 部署及 Linux/systemd 托管源码部署。更新过程包含备份、后台进度与日志、重启、健康检查和失败回滚,保留原有数据、密钥、端口、卷与配置。原生 Windows 源码、Codespaces、前台进程及非 Git 源码目录继续使用手动升级方式。
已完成 Ubuntu 两版与 Mac ARM64 的真实界面升级测试,并验证失败回滚及七语言界面。工具安装任务可跨页面及浏览器刷新恢复,工作台服务重启后不会继续原安装任务。
Detailed first upgrade from v1.0.1
- Stop active tasks, tool installations and SSH sessions. Back up the database together with its matching encryption key, configuration and tool data. Record the existing container/Compose settings, ports, environment and volumes; do not remove volumes.
- Follow the appropriate first-upgrade procedure for your existing deployment: Docker or Compose, or Linux source/systemd. The README includes the exact backup, v1.0.4 migration, verification and rollback commands, including archive or divergent source histories.
- On the host, complete the one-time registration for your deployment using the commands in the upgrade instructions and the platform update guide. These cover SSH prerequisites and Docker or Linux/systemd registration. Keep the existing network-guard configuration where applicable.
- Confirm the upgraded service is healthy and the existing data is available. Sign in as a team administrator and use System settings → Version updates → Check for updates → Update platform for subsequent releases; confirm with the administrator's current password.
中文用户可查看 v1.0.1 → v1.0.4 升级与首次通道配置步骤,其中分别列出 Docker、Compose 和源码部署的完整命令。旧版须先手动升级并注册通道,之后才可在系统设置中更新平台。
APTv1.0.3
AgenticPenTest v1.0.3
A follow-up update to v1.0.2, focused on tool installation, platform compatibility and test scope management.
- Install supported catalog tools directly, individually or in batches, with an optional authenticated proxy.
- Show local execution, dependency-server requirements and platform compatibility explicitly, including Apple Silicon guidance.
- Configure CIDRs and wildcard domains using compact, keyboard-friendly scope tags. Choose HTTP/HTTPS with the themed picker; remove tags through an explicit confirmation dialog.
- Retain network scope validation and gov/edu domain blocking in both personal and team workspaces. Authorization acknowledgement remains enabled.
- Publish Linux amd64 and arm64 images with version and source-commit tags.
Upgrade
Use johncoke/agenticpentest:v1.0.3. Back up configuration and persistent data before updating; keep the existing data and tool volumes. Third-party tool readiness still depends on the actual operating system and installed dependencies.
中文
这是 v1.0.2 的进一步更新:完善内置工具直接下载安装、批量安装与代理设置,明确本地及依赖服务器执行位置,优化测试范围标签、协议选择和删除确认。镜像支持 Linux amd64 / arm64,升级请保留已有配置、数据卷和备份。
APTv1.0.2
Changes
- Download tools from public GitHub repositories with progress, an exact source commit and archive checksum. Repository scripts are not automatically executed; availability checks remain manual.
- Add applicability guidance for 63 tools across six system/architecture combinations, official references and qualified alternatives.
- Fix controls becoming unclickable after navigation or idle synchronization, stale session actions and asset-map redraw loops.
- Read only executable headers during passive compatibility inspection to keep tool-list refresh lightweight.
- Publish native
linux/amd64andlinux/arm64Docker images. Five core ARM64 tools and cloud SDK dependencies were checked on Apple Silicon.
Existing authentication, personal/team isolation and configured network scope checks are preserved. Tool execution still requires a compatible runtime and isolation environment; an ARM64 image does not make every tool compatible with Docker Desktop.