nikopueringer/CorridorKey2.0

Corridor Key 2.0 for all your green and blue screen needs

2.1k stars · 250 forks · Python

Quick update: star history is from the full report of Oct 25, 2026.

Healthy

Maintained by 3 people in the last 90 days, no known risks.

Why

No warning signs: none of the verdict rules applied to this repo.

What would change this

Maintenance

Complete

Steady

Human commits, 30 days
5
Human commits, 90 days
5
Human commits, 365 days
5
Bot share of commits, 365 days
0%
Last commit
Oct 15, 2026 (27 days ago)
Last human commit
Oct 15, 2026 (27 days ago)
Authors, 90 days
3
Last release
none found
Median PR merge time
n/a

Too few recent issues to measure responsiveness.

Sources: Commits, Releases, Merged pull requests, Issues

People

Complete
Owner
Personal account
Commits sampled
5 since Nov 12, 2025
Authors for half of commits
1
Authors for 80% of commits
2
Contributors
2

Top committers

Sources: Commits, Contributors

Stars

Complete

Not enough data, confidence medium

Stars per week, 2026-07-12 to 2026-10-18. 1 weeks overlap a burst.Peak 1.4k a week2026-07-122026-10-18
Bars show stars gained each week. Red bars overlap a burst.

Bursts

Anyone can buy stars for any repo; bursts alone don't prove the owner did.

Sources: How star history is analyzed

Risk

Complete

Flags

No risk flags.

License

Now
No license found
A year ago
Not known

Packages

No published packages found.

Sources: GitHub: nikopueringer/CorridorKey2.0

Compare

Weighing nikopueringer/CorridorKey2.0 against an alternative? See both side by side.

Badge

RepoRadar: Healthy

Add this to a README to show the current verdict:

[![RepoRadar](https://reporadar.ai/nikopueringer/CorridorKey2.0/badge.svg)](https://reporadar.ai/nikopueringer/CorridorKey2.0)

Follow

Get told when this verdict changes. Add the feed to any feed reader: you get one entry per change, not one per refresh.

https://reporadar.ai/nikopueringer/CorridorKey2.0/feed.xml

Open the feed

See all

Earlier verdicts

Computed 9 hours ago · method 2026.10.2