|
HexForge Security Lite is a source-available defensive scanner for passive web security analysis. It transforms visible web signals into structured findings with severity, confidence, evidence, recommendations and human-readable reports. |
Built for signal. Designed for clarity. Limited for safety.
| Section | Purpose |
|---|---|
| Overview | What HexForge Security Lite does |
| Live Demo | Open the hosted Render version |
| Screenshots | Visual proof of the interface and reports |
| Core Philosophy | Why the project exists |
| What It Checks | Passive security review areas |
| How It Works | Internal workflow |
| Report Format | How findings are presented |
| Architecture | Repository and package structure |
| Quick Start | Run locally or with Docker |
| API | Programmatic usage |
| Testing | Local validation |
| Safety Boundaries | Responsible limits |
| Roadmap | Future direction |
| Support | Support development |
HexForge Security Lite is a lightweight passive security analysis platform for reviewing visible web security signals.
It helps developers, learners, researchers and defensive teams identify configuration issues and exposed client-side surface without using destructive techniques.
The goal is not to generate fear.
The goal is to generate understanding.
HexForge Lite focuses on:
- clear findings
- visible evidence
- low-noise reports
- safe passive review
- structured recommendations
- readable risk context
- beginner-friendly interpretation
- professional-looking output
Open the hosted version:
Useful routes:
/
/scanner
/results
/health
/api/meta
/api/scan
Recommended safe target for first testing:
https://example.com
Use HexForge Lite only on systems you own, manage, or have explicit permission to review.
HexForge Security Lite is built around one idea:
A useful security tool should explain what it sees, not just throw alerts.
Many scanners produce overwhelming output.
HexForge Lite is designed to keep findings structured, readable and review-oriented.
Every meaningful finding should answer:
| Question | Why it matters |
|---|---|
| What was observed? | Shows the exact signal |
| Where was it found? | Gives context and location |
| Why does it matter? | Explains the security meaning |
| What should be reviewed? | Provides the next step |
| How confident is it? | Avoids exaggerated claims |
Lite is intentionally conservative.
It performs safe, read-only analysis and avoids intrusive behavior.
The output is designed for people, not only machines.
Findings are written so they can be understood, reviewed and explained.
HexForge Lite focuses on visible and passive web security signals.
Reviews common browser-facing protections such as:
- Content-Security-Policy
- Strict-Transport-Security
- Referrer-Policy
- Permissions-Policy
- X-Content-Type-Options
- iframe and clickjacking-related protections
Observes:
- HTTP status
- HTTPS usage
- redirects
- exposed response metadata
- transport-related clues
- visible configuration gaps
Checks observable cookie attributes:
- Secure
- HttpOnly
- SameSite
- cookie scope
- browser-visible session posture
Identifies permissive or review-worthy CORS behavior and presents it with context.
Extracts visible client-side references:
- routes
- linked scripts
- API-like paths
- forms
- parameters
- same-origin references
- exposed frontend paths
Maps visible forms and parameters without submitting exploit payloads.
Depending on the deployed modules, Lite may observe:
- robots.txt
- sitemap.xml
- security.txt
- HTML metadata
- visible comments
- linked resources
- client-exposed hints
Target URL
β
βΌ
Normalize URL
β
βΌ
Safe HTTP Fetch
β
βΌ
Passive HTML / Header / Surface Review
β
βΌ
Detection Modules
β
βΌ
Validation and Deduplication
β
βΌ
Risk Scoring
β
βΌ
Human-Readable Report
HexForge Lite does not attempt to prove exploitation automatically.
It collects visible signals and presents them for defensive review.
A HexForge Lite finding can include:
| Field | Meaning |
|---|---|
| Severity | Critical, high, medium, low or informational |
| Confidence | How reliable the observation is |
| Location | Where the signal appeared |
| Evidence | What was actually observed |
| Recommendation | What should be reviewed or improved |
| Precision note | Why the finding should not be exaggerated |
| Rule ID | Internal reference for the finding |
Example:
Finding: Missing browser hardening headers
Severity: Medium
Confidence: High
Location: HTTP response headers
Evidence: Missing Content-Security-Policy, Referrer-Policy and Permissions-Policy
Recommendation: Add browser hardening headers based on application behavior.
Precision: Confirmed from the HTTP response, but final impact depends on application context.
HexForge Security Lite is organized as a modular Python project.
hexforge-security-lite/
βββ api/
β βββ handlers
β βββ routes
β
βββ assets/
β βββ branding and visual resources
β
βββ benchmarks/
β βββ benchmark material
β
βββ cli/
β βββ command line entrypoints
β
βββ datasets/
β βββ controlled test and reference data
β
βββ docs/
β βββ documentation
β
βββ examples/
β βββ usage examples
β
βββ frontend/
β βββ frontend resources
β
βββ hexforge_lite/
β βββ engine/
β βββ modules/
β βββ output/
β βββ scoring/
β βββ utils/
β βββ validators/
β βββ config.py
β βββ fetcher.py
β βββ models.py
β βββ plugins.py
β
βββ lab/
β βββ lab resources
β
βββ plugins/
β βββ external or experimental plugin resources
β
βββ rules/
β βββ rule references
β
βββ screenshots/
β βββ landing.png
β βββ scanner.png
β βββ report-overview.png
β βββ evidence-recommendations.png
β
βββ scripts/
β βββ automation and checks
β
βββ tests/
β βββ test suite
β
βββ website/
β βββ index.html
β βββ scanner.html
β βββ results.html
β βββ static.css
β βββ i18n.js
β
βββ Dockerfile
βββ README.md
βββ requirements.txt
βββ run.sh
βββ server.py
git clone https://github.com/BP202302/hexforge-security-lite.git
cd hexforge-security-lite
pip install -r requirements.txt
python3 server.pyOpen:
http://127.0.0.1:10000
If your environment uses a different port, use the port shown in your terminal.
chmod +x run.sh
./run.shdocker build -t hexforge-security-lite .
docker run -p 10000:10000 hexforge-security-liteThen open:
http://127.0.0.1:10000
GET /healthGET /api/metaPOST /api/scan
Content-Type: application/jsonExample request:
{
"target": "https://example.com"
}Example response shape:
{
"ok": true,
"version": "1.9.0-stable",
"target": "https://example.com",
"findings": [],
"risk_score": 0
}Run the test suite:
python3 -B -m unittest discover testsRun self-checks if available:
python3 -B scripts/self_check.pyRecommended before every release:
python3 -B -m unittest discover tests
python3 -B scripts/self_check.pyHexForge Lite can include passive modules for:
| Module Area | Purpose |
|---|---|
| Headers | Browser and HTTP header review |
| TLS / HTTPS | Transport posture observations |
| Cookies | Cookie attribute inspection |
| CORS | Cross-origin policy review |
| Discovery | Visible metadata and discovery files |
| Forms | Passive form mapping |
| Parameters | Query and client-side parameter detection |
| Routes | Visible path extraction |
| API-like references | Client-side endpoint discovery |
| Comments | Passive review of visible HTML comments |
| Metadata | HTML and response metadata review |
| Resources | Linked resource observation |
| Report output | Structured result rendering |
HexForge Lite findings are review guidance, not automatic proof of exploitation.
A missing header may be important.
A permissive CORS policy may require more context.
A visible route may be normal or sensitive depending on the application.
A client-side endpoint may be expected, internal, deprecated or worth reviewing.
The scanner provides the signal.
The reviewer decides the final impact.
HexForge Security Lite is intentionally limited.
- passive fetching
- header analysis
- TLS and HTTP observation
- form discovery
- route discovery
- parameter discovery
- client-side reference mapping
- conservative findings
- readable recommendations
- safe report generation
- brute force
- credential attacks
- destructive exploitation
- unauthorized bypass attempts
- heavy fuzzing
- exploit chaining
- payload automation against third-party targets
- intrusive vulnerability exploitation
Use only on systems you own, manage, or have explicit permission to review.
Check whether a web app exposes visible configuration weaknesses before publishing.
Understand common web security signals through readable evidence.
Use with intentionally vulnerable or controlled targets.
Show a real security tool with UI, API, reports and deployable architecture.
Perform quick passive review of visible posture and browser-facing configuration.
Collect visible findings before deeper authorized manual validation.
HexForge Lite is the public Lite edition of the HexForge ecosystem.
| Edition | Purpose |
|---|---|
| Lite | Public source-available defensive scanner |
| Pro | Future advanced individual workflow |
| Specter | Future premium or enterprise direction |
The Lite repository should remain:
Clean.
Safe.
Readable.
Public-facing.
Useful.
Non-destructive.
Advanced commercial functionality should remain separate from the Lite public repository.
| Version | Focus |
|---|---|
| v1.9.x | Stabilization, cleanup, documentation and demo polish |
| v2.x | Better reports, stronger module organization and improved CLI |
| v3.x | Visual mapping, richer exports and deeper workflow support |
| Pro track | Separate private or commercial direction |
| Specter track | Premium or enterprise direction |
Before publishing a new version:
Run tests
Run self-check
Confirm Render deploy
Confirm /scanner works
Confirm /results works
Confirm README version
Confirm CHANGELOG
Create tag
Create release ZIP
Suggested release names:
v1.9.0-stable
v1.9.1-clean
v1.9.2-stable
v2.0.0-lite
Security tools should not only find things.
They should explain them.
HexForge Lite exists because useful security review needs:
- clear findings
- visible evidence
- safe workflows
- practical recommendations
- controlled scope
- honest severity
- readable reports
- low-noise interpretation
The goal is not to generate fear.
The goal is to generate understanding.
Good contribution areas:
- passive modules
- report readability
- translations
- UI polish
- test cases
- documentation
- safer validation logic
- performance improvements
- false positive reduction
Contributions should preserve the Lite philosophy:
Safe.
Passive.
Readable.
Evidence-first.
Low-noise.
If HexForge Security Lite helps you, you can support development here:
Official site:
HexForge Security Lite is intended for educational, defensive and authorized security review.
Do not use this tool against systems without permission.
You are responsible for your own usage.
HexForge Security Lite is a source-available Lite edition.
Review the repository license before using, modifying, redistributing or deploying this software.
Commercial use may require explicit permission depending on the license terms.



