devsecops-radar 0.4.0

Unified CI/CD Security Dashboard — Pipeline Sentinel

🛡️ Pipeline Sentinel

The Open‑Source DevSecOps Command Center — Unify, Analyse, Remediate.

📖 Read this in: Русский | 中文

---

📖 Table of Contents

1. What Is Pipeline Sentinel? (Simple Explanation)
2. Why You Need It
3. Where to Run It in Your Network
4. Dashboard Preview
5. Quick Start
6. Prerequisites
7. Installation
8. How to Use (Step‑by‑Step)
9. Complete Command Reference
10. Core Capabilities
11. Community Rules & Online Updates
12. Attack Simulation & What‑If Analysis
13. Architecture
14. Roadmap
15. Testing & CI
16. Security Policy
17. Contributing
18. Code of Conduct
19. Author
20. License

---

👨‍👩‍👧 What Is Pipeline Sentinel? (Simple Explanation)

Imagine you have several security guards, each watching a different door of a building. They all shout their findings in different languages, and you have to run around to understand what’s going on.

Pipeline Sentinel puts them all in one room, translates their reports, and shows you a single, clear screen with the full picture. It connects to tools like Trivy (checks your containers), Semgrep (scans your code), Poutine (audits your GitLab pipelines), Zizmor (secures your GitHub Actions), and Gitleaks (finds secrets). Instead of digging through multiple JSON files, you get a beautiful, dark‑mode command‑center dashboard that tells you what’s critical, how risks are trending, and even how an attacker might chain several small issues into a big problem.

Think of it as a security camera system for your entire CI/CD pipeline — it watches everything, alerts you, suggests fixes, and even lets you simulate attack chains, all without needing internet access if you want.

---

💥 Why You Need It

In 2026, supply chain attacks have become the #1 threat. Tools like Trivy themselves were compromised, and attackers now inject malicious code directly into build pipelines. You can no longer just scan your code; you must scan your pipeline.

Pipeline Sentinel gives you:

• One screen for all scanners – stop juggling log files.
• AI that understands attack chains – “A leaked secret + an old library = a disaster.”
• Automatic fixes – with a single flag, it patches files and opens a pull request (with backup).
• Human review mode – inspect each fix before applying.
• Compliance reports – generate a PDF for your boss or auditor.
• Attack simulation – tick a few findings and see a generated attack script.
• 100% offline capable – works in air‑gapped environments where security matters most.
• Interactive wizard – one command to get everything running.
• Community rules marketplace – pull curated detection rules from the community.

---

📍 Where to Run It in Your Network

Pipeline Sentinel is designed to be flexible — you decide where it fits best:

Deployment	Description
🖥️ Local Developer Machine	Run the CLI and dashboard right on your laptop. Perfect for individual pentesters or developers who want instant feedback.
🔧 CI/CD Runner	Use the GitHub Action or call devsecops-radar directly in your Jenkins/GitLab CI scripts. It can fail the build if critical vulnerabilities exceed your policy (--policy).
🏢 Central Security Server	Install on a dedicated server (via Docker or pip) that collects scan results from multiple teams. The dashboard becomes a shared security operations console.
🌐 Air‑Gapped Networks	Copy the Docker image and sample data to an offline server. The dashboard works with zero external calls — all assets are embedded.

Typical Network Flow

[Trivy scan] ──┐
[Semgrep scan] ─┤
[Poutine scan] ─┼──> devsecops-radar (CLI) ──> findings.json ──> Dashboard (Flask) ──> Browser
[Zizmor scan] ─┘
[Gitleaks scan] ┘

📌 Diagram Placeholder:

---

📸 Dashboard Preview

Severity doughnut, trend line chart, attack‑path graph (clickable nodes), topology view, executive summary, and attack simulation panel — all fully offline.

---

🚀 Quick Start

# 1. Install from PyPI
pip install devsecops-radar

# 2. Feed scanner data (sample data is included in the repo)
devsecops-radar --trivy sample_trivy.json --semgrep sample_semgrep.json

# 3. Launch the dashboard
devsecops-radar-web

Open http://localhost:8080 — your unified command center is live with sample findings.

🧙 Want a fully guided setup? Run the wizard:

devsecops-radar --wizard

---

📋 Prerequisites

Pipeline Sentinel relies on external security tools to produce the JSON reports it consumes. You must install these tools separately according to your needs.

Required for offline scanning:

• Trivy (installation)
• Semgrep (installation)
• Poutine (installation)
• Zizmor (installation)
• Gitleaks (installation)

Optional:

• Ollama – for AI‑powered analysis (installation)
• Docker – for attack sandboxing and container scanning
• OPA – for advanced Rego policy evaluation

📖 See PREREQUISITES.md for more details.

---

📦 Installation

Option 1 — PyPI (Recommended)

pip install devsecops-radar

Option 2 — From Source

git clone [https://github.com/Mehrdoost/devsecops-radar.git](https://github.com/Mehrdoost/devsecops-radar.git)
cd devsecops-radar
pip install -e ".[dev]"

Option 3 — Docker

docker pull ghcr.io/mehrdoost/devsecops-radar:latest
docker run -p 8080:8080 ghcr.io/mehrdoost/devsecops-radar:latest

Mount your own findings file:

docker run -p 8080:8080 -v $(pwd)/findings.json:/data/findings.json ghcr.io/mehrdoost/devsecops-radar:latest

Or use Docker Compose:

docker compose up

🧙 One‑Command Install (curl)

curl -fsSL [https://raw.githubusercontent.com/Mehrdoost/devsecops-radar/main/install.sh](https://raw.githubusercontent.com/Mehrdoost/devsecops-radar/main/install.sh) | bash

This script installs Python dependencies, Ollama, pulls the AI model, and starts the wizard.

---

🧭 How to Use (Step‑by‑Step)

1. Run Your Security Scanners

Generate JSON output from your tools:

trivy image --format json -o trivy.json nginx:latest
semgrep --config=auto --json --output semgrep.json .
poutine scan ./repo --format json --output poutine.json
zizmor scan ./repo --output zizmor.json --format json
gitleaks detect --source . --report-format json --report-path gitleaks.json

2. Merge Findings with the CLI

devsecops-radar --trivy trivy.json --semgrep semgrep.json --poutine poutine.json --zizmor zizmor.json --gitleaks gitleaks.json

This produces a single findings.json with all findings merged and normalised.

3. View the Dashboard

devsecops-radar-web

The dashboard shows:

• Severity Breakdown – Doughnut chart
• Trend Over Time – Line chart from scan history
• Pipeline Security – Poutine + Zizmor statistics card
• Attack Path Graph – Interactive D3.js graph (click nodes for details)
• Executive Summary – Risk score and AI‑generated summary
• Findings Table – Searchable, filterable, paginated, with checkboxes for simulation

4. Enable AI Analysis (Optional)

ollama pull llama3.2:latest
devsecops-radar --trivy trivy.json --analyze
devsecops-radar-web

The LLM generates findings_ai_summary.json containing:

• executive_summary, risk_score
• attack_paths with MITRE ATT&CK tactics
• top_remediations (some with fix_diff)
• false_positives_likely

5. Auto‑Remediation (with Human Review)

# Apply fixes automatically
devsecops-radar --trivy trivy.json --analyze --fix

# Review each fix before applying
devsecops-radar --trivy trivy.json --analyze --fix --review

All modified files are backed up to ~/.devsecops-radar/backups/ before any change. The tool creates a new git branch auto-fix and pushes it for review.

6. Policy Enforcement

Create a policy.json file:

{"max_critical": 5, "on_violation": "fail"}

devsecops-radar --trivy trivy.json --policy policy.json

If critical findings exceed 5, the command exits with code 1 — perfect for CI/CD gates.

You can also use OPA Rego policies:

devsecops-radar --trivy trivy.json --rego-policy policy.rego

7. Generate Compliance Reports

devsecops-radar --trivy trivy.json --analyze --compliance CIS --report cis-report.pdf

A PDF report is created with an executive summary, risk score, findings table, and compliance mapping. Sensitive data can be redacted automatically.

8. Security Badge for Your Project

After running a scan, you can embed a dynamic security badge in your README:

[![Security Status](https://your-server/badge/1.svg)](https://github.com/Mehrdoost/devsecops-radar)

The badge color changes based on the number of critical findings (green/yellow/red).

---

📋 Complete Command Reference

devsecops-radar — CLI Flags

Flag	Description	Example
--trivy	Trivy JSON file or image name	--trivy results.json or --trivy nginx:latest
--semgrep	Semgrep JSON file or directory	--semgrep results.json or --semgrep ./src
--poutine	Poutine JSON file or repo path	--poutine results.json or --poutine ./repo
--zizmor	Zizmor JSON file or repo path	--zizmor results.json or --zizmor ./repo
--gitleaks	Gitleaks JSON file or repo path	--gitleaks results.json or --gitleaks ./repo
--rules	Directory with custom JSON rule files	--rules ~/my-security-rules/
--policy	Policy JSON file for gating	--policy policy.json
--rego-policy	OPA Rego policy file	--rego-policy policy.rego
--analyze	Enable LLM analysis (Ollama required)	--analyze
--llm-backend	ollama (default) or litellm	--llm-backend litellm
--llm-model	Model name	--llm-model gpt-4o-mini
--fix	Auto‑apply AI‑suggested fixes (with backup)	--fix
--review	Review each AI fix before applying	--review
--topology	Path to topology JSON file	--topology topology.json
--compliance	Framework: CIS, PCI-DSS, ISO27001	--compliance CIS
--report	Generate PDF report (output filename)	--report security_report.pdf
--output	Output JSON file (default: findings.json)	--output merged.json
--wizard	Interactive first‑time setup wizard	--wizard

devsecops-radar-web — Web Server

devsecops-radar-web                       # Launch on http://localhost:8080
FINDINGS_FILE=my.json devsecops-radar-web # Use a custom findings file
PIPELINE_API_KEY=secret devsecops-radar-web  # Enable API authentication

Usage Examples

# Merge multiple scanner outputs
devsecops-radar --trivy trivy_scan.json --semgrep semgrep_scan.json

# Scan directly (if tools are installed)
devsecops-radar --trivy nginx:latest --semgrep ./src --poutine ./repo

# Merge built‑in scanners with custom rules
devsecops-radar --trivy trivy_scan.json --rules ~/my-security-rules/

# Enable AI analysis (Ollama must be running)
ollama pull llama3.2:latest
devsecops-radar --trivy trivy_scan.json --semgrep semgrep_scan.json --analyze

# Use OpenAI via LiteLLM
export OPENAI_API_KEY=sk-...
devsecops-radar --trivy trivy_scan.json --analyze --llm-backend litellm --llm-model gpt-4o-mini

# Build scan history and view trends
devsecops-radar --trivy sample_trivy.json --semgrep sample_semgrep.json
devsecops-radar --trivy sample_trivy.json --poutine sample_poutine.json
devsecops-radar-web    # Trend chart now shows multiple data points

---

✨ Core Capabilities

🔌 Multi‑Scanner Plugin Architecture

Built‑in support for five scanners with a real plugin system. Third‑party scanners can be installed as separate packages and discovered automatically via Python entry points. An adapter pattern validates all findings with Pydantic.

Scanner	What It Scans	Flag
Trivy	Container images & dependencies	--trivy
Semgrep	Static Code Analysis (SAST)	--semgrep
Poutine	GitLab CI/CD configuration security	--poutine
Zizmor	GitHub Actions workflow security	--zizmor
Gitleaks	Secrets detection	--gitleaks

🧩 Hybrid RuleFusion Engine

• Offline – Load custom JSON rules from any local directory (--rules ~/my-rules/)
• Online – Pull community‑curated rules from a configurable Git repository (--update-rules)
• Auto‑detects Trivy, Semgrep, Poutine, Zizmor, and plain‑list formats
• Policy evaluation built directly into the engine (JSON and OPA Rego)
• Community rules repo: devsecops-radar-rules (configurable via COMMUNITY_RULES_REPO)

🧠 LLM‑Powered Analysis

• Retry logic with exponential backoff for unstable endpoints
• Few‑shot examples covering real‑world supply chain attack chains
• Token‑aware selection (max items configurable via ANALYZER_MAX_FINDINGS)
• Structured JSON output: executive_summary, risk_score, attack_paths (MITRE ATT&CK), top_remediations, false_positives_likely
• Ollama (local, offline) and LiteLLM (OpenAI, Anthropic, etc.) support

🕸️ Multi‑Step Attack Path Visualization

Interactive D3.js force graph that chains findings into realistic attack scenarios. Click any node to see detailed finding information or to trigger a simulation. Accepts a topology file to map findings onto your actual infrastructure, showing lateral movement across servers and subnets.

🛡️ Policy‑as‑Code (JSON & Rego)

Define simple security gates with a JSON file, or write complex rules in Rego for OPA. Fail the pipeline when policies are violated.

🛠️ Auto‑Remediation with Backup & Human‑in‑the‑Loop

AI‑suggested fixes are applied automatically (--fix) or reviewed one‑by‑one (--review). Every modified file is backed up to ~/.devsecops-radar/backups/ before any change. A new git branch is pushed for review.

📊 Compliance & Executive Reports (with Redaction)

Generate professional PDF reports (--report report.pdf) with:

• Executive summary and risk score
• Findings table (first 50 items)
• Compliance mapping (CIS, PCI‑DSS, ISO 27001)
• Automatic redaction of passwords, tokens, JWTs

📈 Scan History & Trends (with Pagination)

SQLAlchemy‑backed database with server‑side pagination (/api/findings?page=1&per_page=50). Scan history is stored efficiently, enabling fast trend charts and historical comparisons.

🧪 SBOM & Dependency Confusion Detection

• Generate a CycloneDX SBOM from your project using syft
• Apply VEX (Vulnerability Exploitability eXchange) files to filter false positives
• Detect dependency confusion risks in package.json and requirements.txt — internal packages that could be impersonated by public registries

🔍 RAG‑Powered Security Search

Ask natural language questions about your scan history: “When was the last Log4j vulnerability found?” The built‑in RAG endpoint (/api/rag?q=...) searches stored findings and returns matches.

📉 Dynamic Risk Scoring

Beyond CVSS, each finding gets a dynamic risk score based on:

• Asset exposure (from topology)
• Exploit availability
• Active threat intelligence feeds

🧙 Interactive Wizard

A --wizard flag walks new users through installing dependencies, pulling AI models, and running their first scan — all in one go.

🔒 Privacy & Offline‑First

• All assets (CSS, JS) are embedded — zero CDN calls
• LLM analysis runs locally with Ollama; no data leaves your network
• Optional API key authentication for the dashboard (JWT supported)
• Docker image runs as non‑root user

---

🌍 Community Rules & Online Updates

Pipeline Sentinel features a community‑driven rule marketplace housed in a separate repository: devsecops-radar-rules.

How It Works

The repository contains curated JSON rule files for all supported scanners (Trivy, Semgrep, Poutine, Zizmor, Gitleaks) and generic compliance checks. Anyone can contribute by submitting a Pull Request with new or improved rules. Users can pull the latest rules with a single command:

devsecops-radar --update-rules

Rules are stored locally in ~/.devsecops-radar/community-rules/. To use them alongside your scanner results:

devsecops-radar --trivy scan.json --rules ~/.devsecops-radar/community-rules/

You can even point to your own fork or a private repository by setting the COMMUNITY_RULES_REPO environment variable. This turns Pipeline Sentinel into a living, community‑improved security platform — just like Nuclei Templates or Semgrep Registry.

Contributing a Rule

1. Fork the devsecops-radar-rules repository.
2. Add a new JSON file to the rules/ directory (or modify an existing one). Follow the standard Pipeline Sentinel finding format (see the repo’s README).
3. Open a Pull Request — our maintainers will review and merge.

---

⚔️ Attack Simulation & What‑If Analysis

New in v0.4.0: Interactive attack simulation directly from the dashboard.

1. Tick the checkboxes next to the findings you want to investigate.
2. Click “⚡ Simulate Selected”.
3. A modal will display a generated attack script (bash), a description of the attack chain, and — if Docker is available — the output of running the script in a sandbox container.

You can also click any node in the Attack Path Graph and press “Simulate this attack” for the same functionality. This feature helps security teams:

• Understand how multiple vulnerabilities can be chained.
• Generate proof‑of‑concept scripts for stakeholders.
• Test mitigations without risking production systems.

---

🏗️ Architecture

devsecops_radar/
├── cli/            # CLI entry point – plugin discovery, policy, remediation
├── core/           # RuleFusion engine, DB (SQLAlchemy), LLM analysers
├── scanners/       # Pluggable scanner classes (extend ScannerPlugin)
├── plugins/        # ScannerPlugin abstract base class & entry points
└── web/            # Flask dashboard (modular Blueprints)
    ├── dashboard/  # Main dashboard routes & embedded HTML
    ├── attack_paths/
    ├── topology/
    ├── summary/
    └── sentry/     # Live webhook agent for CI/CD

📌 Diagram Placeholder:

---

🗺️ Roadmap

Phase	Feature	Status
✅ Phase 1	Multi‑scanner engine (Trivy, Semgrep, Poutine, Zizmor)	Done
✅ Phase 1	LLM analysis (Ollama + LiteLLM)	Done
✅ Phase 1	Scan history, trend chart, scan diff	Done
✅ Phase 1	GitHub Action (composite)	Done
✅ Phase 1	Docker image (multi‑stage, non‑root)	Done
✅ Phase 2	Attack‑path visualization with MITRE ATT&CK & topology	Done
✅ Phase 2	Policy‑as‑Code engine (--policy)	Done
✅ Phase 2	Auto‑remediation engine (--fix) with backup	Done
✅ Phase 2	Compliance reports (PDF) with redaction	Done
✅ Phase 2	Hybrid RuleFusion engine (local + community rules)	Done
✅ Phase 3	Web dashboard Blueprint refactor (modular Flask)	Done
✅ Phase 3	Real scanner plugin system with entry points	Done
✅ Phase 3	SQLAlchemy ORM with pagination	Done
✅ Phase 3	SBOM & Dependency Confusion Detection	Done
✅ Phase 3	RAG‑powered security search	Done
✅ Phase 3	Dynamic Risk Scoring	Done
✅ Phase 3	Interactive wizard (--wizard)	Done
✅ Phase 3	Human review mode (--review)	Done
✅ Phase 3	Gitleaks secret scanner	Done
✅ Phase 3	Security badge endpoint	Done
✅ Phase 3	Full test suite & CI pipeline	Done
✅ Phase 4	Advanced attack simulation (What‑If)	Done
✅ Phase 4	VEX filtering & OPA Rego policies	Done
🔲 Phase 5	Jira / Slack integration	Planned
🔲 Phase 5	SARIF & CycloneDX support	Planned
🔲 Phase 5	Pull Request assistant (GitHub App)	Planned
🔲 Phase 5	eBPF runtime security agent	Planned

See the open issues for a full list of proposed features.

---

🧪 Testing & CI

Pipeline Sentinel is thoroughly tested to ensure reliability for production use.

• Unit & Integration Tests: 23+ tests covering scanners, rule engine, database, analyzer, API, and CLI.
• CI Pipeline: Every push and pull request triggers automated testing (pytest with coverage) and linting (ruff, mypy) via GitHub Actions.
• Code Coverage: We track coverage with Codecov (see badge above).

You can run the tests locally:

pip install -e ".[dev]"
pip install pytest pytest-flask ruff
pytest tests/ -v --cov=devsecops_radar --cov-report=term-missing
ruff check .
mypy .

---

🔒 Security Policy

We take security seriously. If you discover a vulnerability, please report it privately. See our full Security Policy for details on reporting, supported versions, and disclosure procedures.

---

🤝 Contributing

We welcome contributions of all kinds! Please read our Contributing Guide for detailed guidelines on how to set up the project, add new scanners, or submit rule changes. For contributing community rules, see the Community Rules section above. We also have Issue Templates and a Pull Request Template to make the process smooth for everyone.

---

💬 Code of Conduct

This project adheres to the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to the maintainers.

---

👨‍💻 Author

ReverseForge — ( Mehrdoost And Mi0r4 )

---

📜 License

MIT — see LICENSE.

⭐ If this project helps your team ship safer software, drop a star — it makes a real difference.