Policyer - the first JS policy engine

Search for a command to run...

No comments yet. Be the first to comment.
My favourite way to deploy resources on AWS is to use Cloudformation (cf), I'm using CDK/Serverless/SST to create my Cloudformation templates. often you will want to share data between stacks, the recommended way will be stack outputs, to use this ou...
Your team has 14 versions of the same code review skill across 5 repos, with no way to sync them. when one improves, the others don't. drop a folder in .claude/skills/ and pray nothing drifts. source

AI agents are unreasonably good at writing SQL. They get specific error messages, fix their own mistakes in one retry, and can introspect query performance with EXPLAIN ANALYZE before you even ask. No

n8n has over 400 integrations. Zapier claims 7,000+. Every single one was hand-built, tested against a moving API, and will eventually break when that API ships a v2. The entire workflow automation in

Part of the "Your Next Startup" series, where I break down startup ideas I think are worth building. Auth0 sold for \(6.5B. Okta is worth \)15B+. CyberArk, Delinea, BeyondTrust, all printing money fro

For as long as software has existed, we've been building two doors into our systems. Door one: the UI, a carefully designed surface where humans point, click, and occasionally rage-quit. Door two: the

Policyer is an open-source project (more like a vision) I created after being inspired by policy engines that become very popular lately (OPA,Checkov)
Policyer going to focus on providing a platform to run and create meaningful reports, data engagement and a plugin system to let you provide any data, sometimes it can be k8s YAML and in other cases, it can be user data.
checkout the example repo
git clone https://github.com/niradler/policyer-todo
cd policyer-todo
npm i
node cli.js -o ./report.json -p ./checks -i false
Checks format:
---
configuration:
provider: todo-provider
type: resource
resource: todo
payload:
id: 1
checks:
- id: todo-id-check
name: check if todo has an id.
severity: High
steps:
- path: id
condition: equal
utility: isInteger
value: true
- path: id
condition: equal
value: 1
- id: todo-title-check
name: check if todo has a title.
severity: Warning
steps:
- path: title
condition: not
utility: isEmpty
value: true
- id: todo-completed-check
name: check if todo has a valid completed field.
severity: Warning
steps:
- path: completed
condition: includes
value:
- true
- false
A check is a set of conditions or policies to enforce, many utilities can help you build complex policies, and you can also add your own when writing your provider.
Policyer is modular, and by nature prefer to be behind the scene and let you customise the user-facing side by the Provider as best fit to your need.
checkout the example repos, contribution is welcome.