Opsecscan

pip install cognis-opsecscan
opsecscan scan .            # → prioritized findings in seconds

🔎 Example output

Real, reproducible output from the tool — runs offline:

$ opsecscan-emit --version
opsecscan 0.1.0

$ opsecscan-emit --help
usage: opsecscan [-h] [--version] {scan} ...

Scan documents and file metadata for OPSEC leaks (GPS EXIF, author/creator
metadata, unit identifiers, PII).

positional arguments:
  {scan}
    scan      scan files or directories for OPSEC leaks

options:
  -h, --help  show this help message and exit
  --version   show program's version number and exit

Blocks above are real opsecscan output — reproduce them from a clone.

Sample result format (illustrative values — run on your own data for real findings):

{
"results": [
    {
        "id": "123456",
        "title": "Potential SQL Injection",
        "description": "The application is vulnerable to SQL injection attacks.",
        "severity": "high",
        "confidence": 0.8,
        "mitre_attack_id": ["T1059"],
        "cve_ids": ["CVE-2022-1234"]
    },
    {
        "id": "789012",
        "title": "Unvalidated Redirect",
        "description": "The application is vulnerable to unvalidated redirect attacks.",
        "severity": "medium",
        "confidence": 0.6,
        "mitre_attack_id": ["T1048"],
        "cve_ids": ["CVE-2021-1111"]
    }
]
}

Usage — step by step

opsecscan scans documents and file metadata for OPSEC leaks (GPS EXIF, author/creator metadata, unit identifiers, PII). Console script: opsecscan.

1. Install from a clone:

   pip install -e .
   

2. Scan files or directories — recurse with -r:

   opsecscan scan ./release -r
   

3. Tune the threshold — hide low-severity noise and choose what fails the run:

   opsecscan scan ./release -r --min-severity medium --fail-on high
   

4. Read the output — --format json emits per-file findings + a leak count:

   opsecscan scan ./release -r --format json | jq '.leaked, .results[].findings'
   

   Exit codes: 0 clean at/above --fail-on, 1 leak found, 2 usage/IO error.
5. Automate in CI — block a release that leaks metadata:

   - run: pip install -e .
   - run: opsecscan scan ./public -r --fail-on medium
   

Contents

• Why opsecscan? · Features · Quick start · Example · Architecture · AI stack · How it compares · Integrations · Install anywhere · Related · Contributing

Why opsecscan?

Scan documents and file metadata for OPSEC leaks: geotags, author, GPS EXIF, unit identifiers. — without standing up heavyweight infrastructure.

opsecscan is single-purpose, scriptable, and self-hostable: point it at a target, get prioritized results in the format your workflow already speaks (table · JSON · SARIF), gate CI on it, and let agents drive it over MCP.

Features

• ✅ Scan Bytes
• ✅ Scan Path
• ✅ Scan Paths
• ✅ Runs on Linux/macOS/Windows · Docker · devcontainer
• ✅ Ports in Python, JavaScript, Go, and Rust (ports/)

Quick start

pip install cognis-opsecscan
opsecscan --version
opsecscan scan .                       # scan current project
opsecscan scan . --format json         # machine-readable
opsecscan scan . --fail-on high        # CI gate (non-zero exit)

Example

$ opsecscan scan .
  [HIGH    ] OPS-001  example finding             (./src/app.py)
  [MEDIUM  ] OPS-002  another signal              (./config.yaml)

  2 findings · risk score 5 · 38ms

Architecture

flowchart LR
  IN[image / coordinates] --> P[opsecscan<br/>extract + geolocate]
  P --> OUT[location estimate]

Use it from any AI stack

opsecscan is interoperable with every popular way of using AI:

• MCP server — opsecscan mcp (Claude Desktop, Cursor, Cognis.Studio, uncensored-fleet)
• OpenAI-compatible / JSON — pipe opsecscan scan . --format json into any agent or LLM
• LangChain · CrewAI · AutoGen · LlamaIndex — wrap the CLI/JSON as a tool in one line
• CI / scripts — exit codes + SARIF for non-AI pipelines

How it compares

	Cognis opsecscan	typical tools
Self-hostable, no account	✅	varies
Single command, zero config	✅	⚠️
JSON + SARIF for CI	✅	varies
MCP-native (AI agents)	✅	❌
Polyglot ports (JS/Go/Rust)	✅	❌
Open license	✅ COCL	varies

Integrations

Pipes into your stack: SARIF for code-scanning, JSON for anything, an MCP server (opsecscan mcp) for AI agents, and a webhook forwarder for SIEM/Slack/Jira. See docs/INTEGRATIONS.md.

Install — every way, every platform

pip install "git+https://github.com/cognis-digital/opsecscan.git"    # pip (works today)
pipx install "git+https://github.com/cognis-digital/opsecscan.git"   # isolated CLI
uv tool install "git+https://github.com/cognis-digital/opsecscan.git" # uv
pip install cognis-opsecscan                                          # PyPI (when published)
docker run --rm ghcr.io/cognis-digital/opsecscan:latest --help        # Docker
brew install cognis-digital/tap/opsecscan                             # Homebrew tap
curl -fsSL https://raw.githubusercontent.com/cognis-digital/opsecscan/main/install.sh | sh

Linux	macOS	Windows	Docker	Cloud
scripts/setup-linux.sh	scripts/setup-macos.sh	scripts/setup-windows.ps1	docker run ghcr.io/cognis-digital/opsecscan	DEPLOY.md (AWS/Azure/GCP/k8s)

Related Cognis tools

Explore the suite → 🗂️ all 170+ tools · ⭐ awesome-cognis · 🔗 cognis-sources · 🤖 uncensored-fleet · 🧠 engram

Contributing

PRs, new rules, and demo scenarios are welcome under the collaboration-pull model — see CONTRIBUTING.md and SECURITY.md.

⭐ If opsecscan saved you time, star it — it genuinely helps others find it.

Interoperability

{} composes with the 300+ tool Cognis suite — JSON in/out and a shared OpenAI-compatible /v1 backbone. See INTEROP.md for the suite map, composition patterns, and reference stacks.

License

Source-available under the Cognis Open Collaboration License (COCL) v1.0 — free for personal, internal-evaluation, research, and educational use; commercial / production use requires a license ([email protected]). See LICENSE.

---