beelzebub-labs/beelzebub
A secure low code deception runtime framework, leveraging AI for System Virtualization.
2.2k stars · 218 forks · Go
Healthy
Healthy: actively maintained by 7 people, no known risks.
Why
No rule fired.
What would change this
- A dormant maintenance status, a deprecated or archived package, a successor link, or a critical advisory would change this.
Maintenance
CompleteActive
- Human commits, 30 days
- 3
- Human commits, 90 days
- 15
- Human commits, 365 days
- 44
- Bot share of commits, 365 days
- 60%
- Last commit
- Oct 14, 2026 (12 hours ago)
- Last human commit
- Sep 25, 2026 (19 days ago)
- Authors, 90 days
- 7
- Last release
- Sep 23, 2026 (21 days ago)
- Median PR merge time
- 28 hours
Responsiveness: of 1 recent issues, n/a got a maintainer reply. Median first response: n/a.
- Most commits in the last year come from bots.
- Only 1 recent issues can be checked for a response, too few to measure response time.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Organization
- Commits sampled
- 44 since Oct 15, 2025
- Authors for half of commits
- 2
- Authors for 80% of commits
- 7
- Contributors
- 21
Top committers
- mariocandela: 39% of commits
- airscripts: 11% of commits
- YOZZOPANOZZO: 9% of commits
- zgsec: 9% of commits
- gzigurella: 7% of commits
Sources: Commits, Contributors
Stars
CompleteMostly organic, confidence medium
Bursts
- Jul 14, 2023 to Jul 20, 2023: about 158 more stars than usual, peak 37 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Apr 21, 2024 to Apr 21, 2024: about 11 more stars than usual, peak 11 in one day, a spike that tapers off. No outside explanation found, so this burst is unexplained.
- Feb 10, 2025 to Feb 12, 2025: about 77 more stars than usual, peak 38 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Apr 1, 2025 to Apr 3, 2025: about 87 more stars than usual, peak 50 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- May 26, 2025 to May 26, 2025: about 37 more stars than usual, peak 38 in one day, a spike that tapers off. No outside explanation found, so this burst is unexplained.
- Jul 9, 2025 to Jul 9, 2025: about 29 more stars than usual, peak 30 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jul 23, 2025 to Jul 23, 2025: about 16 more stars than usual, peak 18 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Sep 9, 2025 to Sep 10, 2025: about 57 more stars than usual, peak 45 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
Anyone can buy stars for any repo; bursts alone don't prove the owner did.
- Some star bursts have no matching forks, issues, releases, or launch coverage.
- Anyone can buy stars for any repo, so this describes the star history only.
Sources: How star history is analyzed
Risk
CompleteFlags
No risk flags.
License
- Now
- GPL-3.0 (OSI-approved)
- A year ago
- GPL-3.0 (OSI-approved)
Packages
- github.com/beelzebub-labs/beelzebub/v3 (GO): latest v3.9.2, published Sep 21, 2026
Advisories for the latest version: none listed
Package and advisory data: deps.dev and OSV.
Sources: GitHub: beelzebub-labs/beelzebub, deps.dev: Go github.com/beelzebub-labs/beelzebub/v3
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/beelzebub-labs/beelzebub)Earlier verdicts
- Oct 15, 2026: Healthy
- Oct 14, 2026: Healthy
Computed 2 hours ago · method 2026.10.2