Repository intelligence
ShaftHQ/SHAFT_ENGINE
GitHubA modular, configuration-first Java test automation framework that orchestrates UI, mobile, API, database, CLI, and native desktop testing with unified execution evidence.
CLOUDM0N decision
Trust FAIL · 0/100
Good fit if
Java QA and automation engineers seeking a unified framework to test across Web, Mobile, API, CLI, Database, and native desktop environments
Watch out for
You are building automation suites in languages other than Java
Practical intelligence
What matters before you adopt it
Problem it solves
The repetitive plumbing and fragile setup overhead around drivers, wait conditions, assertions, configurations, test data, and disconnected execution evidence in automation suites.
Best for
Java QA and automation engineers seeking a unified framework to test across Web, Mobile, API, CLI, Database, and native desktop environments
Teams looking to eliminate boilerplate code around driver management, wait conditions, assertions, and reporting in long-lived test suites
AI coding agents requiring structured first-party tools and MCP/CLI skills to plan, author, run, and diagnose test workflows
Main trade-offs
You are building automation suites in languages other than Java
Why it stands out
Eliminates repetitive plumbing around drivers, waits, assertions, configurations, test data, and reports
Modular Maven reactor allows starting lean with the core engine and adding visual, video, cloud, or agentic modules incrementally
Supports heterogeneous test flows combining REST, GraphQL, Database, CLI, and desktop actions in one test
Trust & CVEs
Security evidence without the noise
Trust remains a decision signal; CVEs and scanner evidence explain what is driving the risk.
Security findings
6
CLOUDM0N scanner findings
Critical
1
High
2
Medium
3
Low
0
View trust evidence & security findings▼
Why this score
No trust rationale was stored for this scan.
CLOUDM0N findings
CRITICAL
Private-key material appears to be committed in executable/config scope. 3 sample match(es) found.
HIGH
Remote download piped or chained into a shell requires manual review. 5 sample match(es) found.
HIGH
Container configuration requests host-level control or isolation bypass. 4 sample match(es) found.
MEDIUM
Dynamic code execution pattern detected. 5 sample match(es) found.
MEDIUM
The project can spawn operating-system processes; review command construction and input handling. 5 sample match(es) found.
MEDIUM
Broad permission or elevated-command pattern detected. 5 sample match(es) found.
Architecture from code28 modules · 1 edges▼
Structural evidence
Modules and dependency edges extracted from repository code. This is code evidence, not README inference.
Code files
248
Modules
28
Dependency edges
1
Core modules
chaos-engine
plugins
scripts
shaft-capture
shaft-engine
shaft-upgrader
tools
tool implementations
Dependency flow
No dependency edges were extracted.
Detected languages
Java · Python · Shell · JavaScript · SQL
Detected frameworks
—
Architecture evidence details
flowchart TD
%% repo — high-level architecture (DRAFT, refine me)
n0["chaos-engine · 12 files"]
n1["plugins · 15 files"]
n2["scripts · scripts · 91 files"]
n3["shaft-capture · 1 file"]
n4["shaft-engine · 6 files"]
n5["shaft-upgrader · 1 file"]
n6["tests · tests · 114 files"]
n7["tools · tool implementations · 8 files"]
n6 --> n2
class n2 infra
class n7 shared
class n6 test
classDef infra fill:#b35c00,color:#ffffff,stroke:#8f4a00
classDef shared fill:#79706e,color:#ffffff,stroke:#5d5654
classDef test fill:#499894,color:#ffffff,stroke:#397975Evidence, security & integrations▼
Integrations
SeleniumAppiumRESTGraphQLTestNGJUnitCucumberBrowserStack
Security notes
• Guarded by an automated pull-request gate workflow (.github/workflows/pr-gate.yml)
• Vulnerability reporting is governed by a dedicated security policy (SECURITY.md)
Still unknown
• The README does not state any trade-offs, operational limitations, or drawbacks of adopting SHAFT.
• Does not specify minimum Java runtime or Maven version requirements.
• The exact execution command to run the generated Maven project is missing from the getting started instructions excerpt.
Adoption guidance▼
Adopt if
+ You are using Java and want a framework that automatically manages driver instances, wait behaviors, and test environment synchronization
+ You need to test multiple surfaces (like API, UI, CLI, and Databases) within the same cohesive test flow
+ You want robust execution evidence like screenshots, video, and logs integrated directly into your test run lifecycle
Avoid if
– You are building automation suites in languages other than Java
– You require a lightweight setup with zero framework dependencies or a non-Maven ecosystem
How it works & getting started▼
How it works
1.The user generates a pre-configured Maven project template from the SHAFT landing page
2.Test intent and configuration enter SHAFT's unified orchestration layer
3.SHAFT automatically handles and synchronizes underlying Selenium or Appium drivers and execution surfaces
4.Tests execute across one or multiple targeted interfaces (Web, Mobile, API, CLI, or DB)
5.Execution telemetry, screenshots, and log attachments are captured continuously
Getting started
→ Open the SHAFT landing page (https://shafthq.github.io/) and generate a ready-to-run Maven project
→ Extract the generated project files locally
→ Inspect the sample result, screenshots, logs, and Allure evidence
Agent handoff
Use with any agent
Alternatives
Nearby repositories worth comparing before adoption.
playwright
microsoft/playwright
63
Fit
Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
Trust REVIEW · 45
Compare →dbeaver
dbeaver/dbeaver
79
Fit
Free universal database tool and SQL client
Trust PASS · 100
Compare →appwrite
appwrite/appwrite
63
Fit
Appwrite® - complete cloud infrastructure for your web, mobile and AI apps. Including Auth, Databases, Storage, Functions, Messaging, Hosting, Realtime and more
Trust REVIEW · 65
Compare →