microsoft/RulesEngine

A fast and reliable .NET Rules Engine with extensive Dynamic expression support

View on GitHub ↗Jump to charts ↓

microsoft/RulesEngine has 4k+ stars and 600+ forks on GitHub, is written in C#, and was last pushed on Sep 11, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 16th, 2026
Created on July 30th, 2019
Open Issues & Pull Requests: 54 (+0)
GitHub issues: Enabled
Number of forks: 615
Total Stargazers: 4,363 (+0)
Total Subscribers: 103 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.2 days
Mean response time: 89.8 days
90th percentile: 224.4 days
Tracked items: 51

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 463 days
Stale 30+ days: 12
Stale 90+ days: 11

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • needs investigation (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Rules Engine is a .NET rules engine that evaluates dynamic expressions to determine outcomes based on configurable rule sets.

The tool solves the problem of embedding business logic evaluation into applications without hardcoding conditional statements. It allows developers to define rules as JSON or programmatically, where each rule contains conditions expressed in a dynamic expression language. When rules are executed against input data, the engine evaluates conditions in order and returns which rules matched, enabling applications to respond dynamically to changing business requirements without recompilation.

The project suits scenarios where business rules need to be modified frequently or managed by non-technical stakeholders. It works well for workflow engines, decision systems, and any application where rule logic should be externalized from code. Teams building systems that require rapid iteration on conditional logic or multi-tenant applications where different customers need different rules will find this approach valuable. The tool is particularly useful when rules are complex enough that simple if-else chains become unmaintainable but not so complex that a full business process engine is warranted.

Development on the project shows consistent activity with regular commits addressing bug fixes and feature additions. The maintainers respond to issues and pull requests, indicating active stewardship of the codebase. The project maintains comprehensive documentation including API references and usage examples. Updates to dependencies and compatibility improvements appear regularly, suggesting the tool is kept current with the .NET ecosystem. The project accepts community contributions and incorporates feedback from users reporting issues or requesting enhancements.