CacheControl/json-rules-engine

A rules engine expressed in JSON

View on GitHub ↗Jump to charts ↓

CacheControl/json-rules-engine has 3k+ stars and 500+ forks on GitHub, is written in JavaScript, and was last pushed on Feb 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on January 26th, 2016
Open Issues & Pull Requests: 68 (+0)
GitHub issues: Enabled
Number of forks: 509
Total Stargazers: 3,143 (+0)
Total Subscribers: 69 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.3 days
Mean response time: 138.4 days
90th percentile: 250.0 days
Tracked items: 18

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 16
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 897 days
Stale 30+ days: 16
Stale 90+ days: 16

Recent activity

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

Top labels

  • enhancement (1)
  • next-major (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

json-rules-engine is a rules engine that evaluates conditions and executes actions based on rules defined in JSON format.

The tool solves the problem of embedding business logic into applications without hardcoding conditional statements. It allows developers to define rules as JSON objects that specify conditions to evaluate and corresponding actions to execute. The engine parses these JSON rules and processes them against provided data, returning results based on which rules match the given conditions. This approach decouples business rules from application code, making it easier to modify logic without redeploying the application.

The project suits teams that need to implement configurable business logic, such as eligibility checks, workflow automation, or decision trees. It works well when rules need to be updated frequently or managed by non-technical stakeholders. The JSON-based format makes rules human-readable and can be stored in databases or configuration files. This tool is appropriate for applications where rule complexity is moderate and performance is not the primary constraint, such as validation systems, notification triggers, or conditional feature flags.

The project shows consistent maintenance with regular updates addressing bug fixes and feature requests. Development activity demonstrates responsiveness to user-reported issues and a willingness to incorporate community feedback. The codebase maintains backward compatibility while gradually improving the engine's capabilities. The maintainers engage with pull requests and clarify expected behavior through issue discussions, indicating an active stewardship of the project's direction.