open-flow

Build workflows you can see, code, run, and own. Open-source visual workflow automation with real TypeScript, isolated execution, and a self-hosted Control API.

Not yet testedsource: GitHubhomepageTypeScriptApache-2.0commit 29c74de02e6d

TypeScript, Apache-2.0 licensed. The project labels itself: automation, cron, docker, integrations, javascript, nodejs, oomol and orchestration.

open-flow has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
226
forks
24
open issues
4
watchers
3
size
14 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

No recorded runs.

Topics (from GitHub)

automationcrondockerintegrationsjavascriptnodejsoomolorchestrationreactself-hostedtypescriptvisual-programmingwebhookworkflowworkflow-automationworkflow-engineworkflows

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/open-flow.svg)](https://argusic.com/subject/open-flow)

Questions

Does open-flow run?
open-flow has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test open-flow?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for open-flow?
All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion