
Security News
curl Shuts Down Bug Bounty Program After Flood of AI Slop Reports
A surge of AI-generated vulnerability reports has pushed open source maintainers to rethink bug bounties and tighten security disclosure processes.
ts-rule-engine
Advanced tools
Lightweight rule engine, written in typescript
{
"node": "18.x || 20.x || 22.x",
}
npm install ts-rule-engine
pnpm add ts-rule-engine
yarn add ts-rule-engine
bun add ts-rule-engine
A rule will consist of a condition and action, id, name and weight. The condition is a function that returns a boolean value. The action is a function that will be executed if the condition is true. The action function will be passed the fact, { rule, stop }. The stop function will stop the rule engine from executing further rules. This way you can control the flow of the rule engine.
import type { Rule } from 'ts-rule-engine'
/* Define fact interface */
interface Fact {
balance: number
broke?: boolean
}
/* Define rule */
const rule: Rule<Fact> = {
id: 1,
name: 'Rule 1',
weight: 1,
condition: (fact) => {
return fact.balance < 5
},
action: (fact, { stop }) => {
fact.broke = true
/* stop() will stop the rule engine from executing further rules */
stop()
}
}
Higher the weight of the rule, higher the priority of the rule. If the weight is not provided, it will be set to 0 by default and will be executed after all the rules with weight > 0 are executed. If all weights are same, rules will be executed in the order they are added to the rule engine.
Facts are those input json values on which the rule engine applies its rule to obtain results. A fact can have multiple attributes as you decide.
A sample Fact may look like
/* Define fact interface */
interface Fact {
application: string
cost: number
license?: string
description?: string
}
/* Define fact */
const fact: Fact = {
application: 'ts-rule-engine',
cost: 0
}
The example below shows how to use the rule engine to apply a sample rule on a specific fact. Rules can be fed into the rule engine as Array of rules or as an individual rule object.
import { RuleEngine } from 'ts-rule-engine'
/* Define fact */
const fact: Fact = {
application: 'ts-rule-engine',
cost: 0,
license: '',
description: ''
}
/* Define rule */
const rule: Rule<Fact> = {
condition: (fact) => {
return fact.cost === 0
},
consequence: (fact) => {
fact.license = 'MIT'
fact.description = 'License originating at the Massachusetts Institute of Technology (MIT) in the late 1980s'
fact.stop()
},
};
/* Creating Rule Engine instance */
const engine = new RuleEngine(fact)
engine.addRule(rule)
/* For multiple rules, use engine.addRules(rules) */
await engine.run()
console.log(fact)
/*
{
application: 'ts-rule-engine',
cost: 0,
license: 'MIT',
reason: 'License originating at the Massachusetts Institute of Technology (MIT) in the late 1980s'
}
*/
The example below shows how to use the rule engine with a custom logger. The logger should implement the Logger interface. If a logger is not provided, logs are written using the global console object.
import { RuleEngine, Logger } from 'ts-rule-engine'
/* Define fact */
const fact: Fact = {
application: 'ts-rule-engine',
cost: 0,
license: '',
description: ''
}
/* Define rule */
const rule: Rule<Fact> = {
condition: (fact) => {
return fact.cost === 0
},
action: (fact, { logger }) => {
logger.info('All Good')
fact.license = 'MIT'
fact.description = 'License originating at the Massachusetts Institute of Technology (MIT) in the late 1980s'
fact.stop()
},
};
/* Custom Logger */
class CustomLogger implements Logger {
messages: string[] = []
info(message?: string, ...optionalParams: string[]): void {
this.messages.push(message)
}
warn(message?: string, ...optionalParams: string[]): void {
this.messages.push(message)
}
error(message?: string, ...optionalParams: string[]): void {
this.messages.push(message)
}
}
/* Creating Rule Engine instance */
const logger = new CustomLogger()
const engine = new RuleEngine(fact, {logger})
engine.addRule(rule)
/* For multiple rules, use engine.addRules(rules) */
await engine.run()
// Check logger messages
console.log(logger.messages)
/*
[
'Rule 1: Executing',
'Rule 1: Executed',
'Rule 1: Stopped'
]
*/
FAQs
Lightweight rule engine, written in typescript
We found that ts-rule-engine demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
A surge of AI-generated vulnerability reports has pushed open source maintainers to rethink bug bounties and tighten security disclosure processes.

Product
Scan results now load faster and remain consistent over time, with stable URLs and on-demand rescans for fresh security data.

Product
Socket's new Alert Details page is designed to surface more context, with a clearer layout, reachability dependency chains, and structured review.