C++ parser generator for dissecting protocols & files.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 73%
Response Time: 7d
First Timer Success: 67%
zeek/spicy has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zeek/spicy respond to incoming external pull requests in approximately 156.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 56.7 places zeek/spicy in the A tier.
The external contributor pull request merge rate for zeek/spicy is 72.9%, based on public PR activity from non-core contributors.
zeek/spicy currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in zeek/spicy. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/zeek/spicy?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~102 hours (91% approval). Large PRs (>500 lines) take ~753 hours (33% approval). Keep your diff compact for rapid review.
This Spicy program gets an internal error, probably not good to expose those to users: module Test; type X = vector<uint32>; public type PubData = unit { : X; }; error: $ spicyc -c test.spicy [internal-error] vectors must only have sub-item, not an inner type --- Aborting # [0x7f70de6b74a5] hilti::rt::Backtrace::Backtrace() # [0x7f70de42b984] hilti::util::abortWithBacktrace() # [0x7f70de420a0b] # [0x7f70df826fe4] # [0x7f70df82dd32] # [0x7f70df812e4e] spicy::type::unit::item::Field::dispatch(hilti::visitor::Dispatcher&) # [0x7f70df6b2355] hilti::visitor::Visitor<(hilti::visitor::Order)0, spicy::visitor::Dispatcher>::dispatch(hilti::Node*) # [0x7f70df832717] # [0x7f70df83283c] spicy::detail::validator::validatePost(hilti::ExtendedBuilderTemplate<spicy::BuilderBase>*, hilti::ASTRoot*) # [0x7f70df7fdc99] # [0x7f70df7fdcc5] # [0x7f70de08a4bf] # [0x7f70de087205] hilti::ASTContext::_validate(hilti::Builder*, hilti::Plugin const&, bool) # [0x7f70de084d5f] hilti::ASTContext::processAST(hil
We document minimum compiler version requirements and check the same numbers in spicy/cmake/CheckCompiler.cmake Lines 4 to 16 in fd21eab # 9.0 works # 10.x is untested set(clang_minimum_version "9.0") # 11.0 comes with 10.15 (Catalina) and works set(apple_clang_minimum_version "11.0") # 7.x is not compiling HILTI/Spicy, although the standard library seems to be recent enough. # 8.x is untested. # 9.1.1 works. set(gcc_minimum_version "8.3"
Both bytes and stream have a sub operator which they can use to return a subrange from offsets: spicy/hilti/toolchain/src/ast/operators/bytes.cc Lines 742 to 769 in 9903fc6 class SubOffsets : public BuiltInMemberCall { public: Signature signature(Builder* builder) const final { return Signature{ .kind = Kind::MemberCall, .self = {.kind = parameter::Kind::In, .type = builder->typeBytes()}, .member = "sub", .param0 = { .name = "beg
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to zeek/spicy, 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 zeek/spicy acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.9% were successfully merged into the primary branch.
zeek/spicy has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 56.7 places zeek/spicy in the Welcoming tier.
The external pull request merge rate is 72.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, zeek/spicy currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for zeek/spicy 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.