Repo brief: microsoft/RulesEngine

Generated by RepoPilot · document generated 2026-09-14 · concise human review Evidence snapshot · analyzed 2026-09-14T10:14:19.164Z · commit 89f9bcd1f94f

Verdict

Healthy — Strong maintenance signals

• Last commit 3w ago
• 24+ active contributors
• Distributed ownership (top contributor 32% of recent commits)
• MIT licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Rules Engine is a .NET library that externalizes business logic from application code by allowing rules to be defined in JSON schemas and executed dynamically via lambda expressions or other expression types. It decouples rule definitions from core system logic, enabling non-developers to modify business policies (discounts, eligibility checks, pricing) without recompiling code. The engine evaluates rules against input objects and returns structured result trees showing which rules succeeded or failed. Standard .NET solution structure: RulesEngine.sln at root with src/ containing the core engine library, demo/ folder with BasicDemo.cs, JSONDemo.cs, NestedInputDemo.cs showing usage…

Start here

Open these first:

• src/RulesEngine/RulesEngine.cs — Main entry point and orchestrator of the rules engine; all rule execution flows through this class
• src/RulesEngine/Models/Rule.cs — Core domain model defining rule structure; understanding this is essential for working with the framework
• src/RulesEngine/ExpressionBuilders/RuleExpressionParser.cs — Parses and compiles dynamic expressions into executable delegates; critical to expression evaluation logic
• src/RulesEngine/Interfaces/IRulesEngine.cs — Public interface contract defining the rules engine API that all consumers depend on
• src/RulesEngine/Actions/ActionFactory.cs — Factory for creating rule actions; extension point for custom business logic execution

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the repo, navigate to solution root, and use .NET tooling: git clone https://github.com/microsoft/RulesEngine.git && cd RulesEngine && dotnet restore && dotnet build. For demos, run `dotnet run --project demo/De…

Daily commands:

For demos: dotnet run --project demo/DemoApp/DemoApp.csproj executes BasicDemo, EFDemo, JSONDemo, NestedInputDemo scenarios. For benchmarks: `dotnet run --project benchmark/RulesEngineBenchmark/RulesEngineBenchmark.cs…

…shortened for this brief.

Key cautions & unknowns

• Lambda expression injection risk: user-supplied rule expressions are evaluated dynamically; if expressions come from untrusted sources (e.g., end-user UI rule builders), arbitrary code execution is…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.