npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@fensak-io/reng

v2.0.2

Published

Fensak Rules Engine, which drives execution of user defined rules on the Fensak platform.

Downloads

7

Readme

fensak-io/reng - Fensak Rules Engine

This is the source code for the Fensak Rules Engine which drives execution of user defined rules on the Fensak platform.

Using @fensak-io/reng for testing Fensak rules

Refer to the Testing your rule functions section in our Writing rules scripts guide for an overview of how to use this package for testing rule functions.

Reporting Bugs, Getting Help, Providing Feedback, etc

Please create a GitHub discussion if you want to:

  • report issues with the hosted Fensak service
  • get any kind of help, like setting up Fensak, writing custom rules, or using Fensak in general
  • provide product feedback and suggestions

Please create a GitHub issue to report bugs and issues with the reng library, including self-hosting and using the functions for testing.

Do not open an issue to report security issues. Instead, please review our Security Policy.

If you are a paying customer of our GitHub App, and have questions about your account, or have any kind of billing releated inquiry, please email [email protected].

LICENSE

SPDX-License-Identifier: AGPL-3.0-or-later OR BUSL-1.1

reng is dual-licensed under the AGPL 3.0 (or any later version) and Business Source License 1.1 (with no Additional Use Grant). Refer to the corresponding LICENSE files for the full parameters of either license:

Dual licensing means that you can use the code under the terms of either license.

For example, if you are using this to test your rules functions and you do not want to be bound by the terms of the AGPL license (and thus be forced to release the source code of your rules), you can license the reng code under the BUSL 1.1 license.

On the other hand, if you wish to use reng in an internal-use only or open source service, then you can license reng under the terms of the AGPL 3.0 (or later) license. You can not use reng in this manner under the BUSL 1.1 license since it does not allow any additional use grant for production usage.

Refer to the License FAQ for more information.