0
/ 100
Polished work that hasn't found its audience yet.
An open-source, self-hosted AI-powered SIEM, EDR and SOAR platform for modern security operations.
Documentation
99
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under AGPL-3.0.
Engineering
86
Test files detected (pytest.ini).
Lockfile present (requirements.txt). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (frontend/eslint.config.js).
Issue or PR templates present.
Project health
100
Dependency manifest found (requirements.txt).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 5Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files27 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- ai
- certs
- core
- docs
- frontendGood: Linter or formatter configured (frontend/eslint.config.js).
- modules
- scanners
- Sentora
- tests
- .dockerignore
- .env.example
- .gitignoreGood: .gitignore present.
- ai_worker.py
- app.py
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- docker-compose.yaml
- DockerfileGood: Environment pinned via Dockerfile.
- init_userdb.sql
- init.sql
- LICENSEGood: Licensed under AGPL-3.0.
- pytest.iniGood: Test files detected (pytest.ini).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- requirements-dev.txt
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- SECURITY.mdGood: Security policy present.
- server.py