StackGuardian/tirith - Open Source PR Review Scorecard

Plugin IaC Governance for any pipeline, running anywhere. Evaluate plans with Tirith, protect sensitive values, enforce centralised governance, and surface actionable results before infrastructure changes are applied.

C-Rank Grade: S (Elite) - 71/100

External PR Merge Rate: 47%

Response Time: 2h

First Timer Success: 100%

Frequently Asked Questions

Is StackGuardian/tirith welcoming to first-time open-source contributors?

StackGuardian/tirith has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in StackGuardian/tirith respond to incoming external pull requests in approximately 1.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 71.1 C-Rank™ score (S Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 71.1 places StackGuardian/tirith in the S tier.

What is the external contributor pull request merge rate for StackGuardian/tirith?

The external contributor pull request merge rate for StackGuardian/tirith is 47.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in StackGuardian/tirith?

StackGuardian/tirith currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

StackGuardian
StackGuardian/tirithS•Elite167
GitHub
Back to Explorer
StackGuardian

StackGuardian/tirith

167
Active (30d)S•Elite(71/100)Low Sample (<20 PRs)Python

Plugin IaC Governance for any pipeline, running anywhere. Evaluate plans with Tirith, protect sensitive values, enforce centralised governance, and surface actionable results before infrastructure changes are applied.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Architecture Gatekeeper

Warmth Score
6.4/10
Patience Score
7.4/10
Nitpick Rate
45%

Strict review standards in StackGuardian/tirith. Ensure PR scope matches issue requirements closely before requesting review.

What Contributors Actually Say

Discussions in StackGuardian/tirith focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Add or update tests for changed behavior before requesting review
  • •Update docs or README when behavior changes
  • •Link the issue and include reproduction context in the PR

Top PR Friction Pitfalls (Don'ts)

  • •Do not leave requested test coverage unresolved
  • •Do not ship user-facing changes without matching docs
  • •Do not open context-free PRs
Response Velocity
1 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
47.4%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
7 core
Highly collaborative maintainer core
Diagnostic Health HUD
47.4%
Merge Gauge
100.0%
1st-Timer
Community Vibe77/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for StackGuardian/tirith
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/StackGuardian/tirith)](https://getmerged.abhishekco.de/StackGuardian/tirith?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Problem The tirith ui playground ships five examples and none is a security check beyond S3 and tags. October is Cybersecurity Awareness Month; a concrete, runnable security policy makes a good addition. What to change Add src/tirith/tui/examples/06-rds-not-public/ with about.md, policy.json and input.json, following 02-no-public-buckets/. The policy fails when any aws_db_instance has publicly_accessible = true The input is a trimmed Terraform plan JSON with one public and one private instance Done when tests/tui/test_examples.py passes and the example appears in tirith ui. Comment to claim this issue and wait to be assigned. Unclaimed or inactive for 3 days, it returns to the pool. Run pytest tests/ and black --line-length 120 before opening the PR.

📅 Opened Oct 2, 2026💬 4 comments
Quality: 90/100Contribute

Problem Workflows pin old action majors, which run on deprecated Node runtimes: actions/checkout@v2/@v3, actions/setup-python@v2/@v4, actions/setup-node@v3. What to change In .github/workflows/build_test.yml, coverage.yml, deploy_docs.yml, lint.yml and pydosctyle.yml, move to actions/checkout@v4, actions/setup-python@v5 and actions/setup-node@v4. Leave third-party actions alone. Done when All workflows pass on the PR and no workflow references checkout@v2/@v3 or setup-python@v2/@v4. Comment to claim this issue and wait to be assigned. Unclaimed or inactive for 3 days, it returns to the pool. Run pytest tests/ and black --line-length 120 before opening the PR.

📅 Opened Oct 2, 2026💬 3 comments
Quality: 90/100Contribute

Problem test_greater_than.py, test_greater_than_equal_to.py, test_less_than.py and test_less_than_equal_to.py in tests/core/evaluators/ each test one pass and one fail with integers. Nothing covers None, floats, equal values or mixed types, where > raises and the evaluator falls back to the exception message. What to change Tests only; no evaluator code changes. If a case exposes a wrong verdict, note it in the PR and we'll open a follow-up. Done when Each of the four files covers: equal values, floats, None input, and a string compared with a number. Comment to claim this issue and wait to be assigned. Unclaimed or inactive for 3 days, it returns to the pool. Run pytest tests/ and black --line-length 120 before opening the PR.

📅 Opened Oct 2, 2026💬 4 comments
Quality: 90/100Contribute

Problem Prefix and suffix checks ("bucket names start with acme-", "AMI names end with -hardened") need a RegexMatch with anchors today, which is easy to get wrong. What to change Add starts_with.py and ends_with.py under src/tirith/core/evaluators/ Register both in EVALUATORS_DICT in src/tirith/core/evaluators/__init__.py and in src/tirith/tui/schema.py Add a row and a section for each in documentation/docs/tirith-reference/evaluators.md Non-string input returns passed: false with a message naming the type Done when One test file per evaluator under tests/core/evaluators/ covers pass, fail, empty string and non-string input. Comment to claim this issue and wait to be assigned. Unclaimed or inactive for 3 days, it returns to the pool. Run pytest tests/ and black --line-length 120 before opening the PR.

📅 Opened Oct 2, 2026💬 4 comments
Quality: 90/100Contribute

Most functions in the project still lack docstrings. Contributions welcome — a good starting point is src/tirith/core/ and each provider's handler.py. Rules for contributing Use the reST docstring format: """ Short description. :param param1: what it is :returns: what is returned :raises KeyError: when it raises """ One file per PR, so contributors don't collide on the same file. Mention this issue in your PR description (e.g. Related to #<this issue>). PR/commit title format: <name of the file>.py: Add docstring.

📅 Opened Sep 4, 2026💬 1 comment
Quality: 90/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for StackGuardian/tirith

When evaluating whether to contribute to StackGuardian/tirith, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of StackGuardian/tirith acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 47.4% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to StackGuardian/tirith

01

Is StackGuardian/tirith welcoming to first-time open-source contributors?

StackGuardian/tirith has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~1 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 71.1 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 71.1 places StackGuardian/tirith in the Elite tier.

04

What is the external contributor pull request merge rate for StackGuardian/tirith?

The external pull request merge rate is 47.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in StackGuardian/tirith?

Yes, StackGuardian/tirith currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for StackGuardian/tirith are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.