LiteFlow

Lightweight, fast, stable, programmable component-based rule engine — where AI Agents orchestrate just like ordinary com

Workflow Platforms Java Grade C Listed Apache-2.0
51.7/100
Rank #300 of 468
Compare LiteFlow

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-07-31 · 6d ago
Recent change
No recent signal change

Is LiteFlow safe? LiteFlow scores 51.7/100 (Grade C), ranked #300 of 468 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.0/10; 1% of recent commits are signed; last pushed 2026-07-31. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Workflow Platforms

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-28
Grade Changed
Trust grade D → C
2026-07-28
Rank Moved
Rank rose 42 spots (#333 → #291)
2026-07-28
HVTrust Changed
HVTrust up 6.4pts (45.8 → 52.2)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
82.4
Activity sub-score · out of 100
#19

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-06 05:00 UTC · Repo last pushed 6 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
3.8k
Forks
522
Last Push
2026-07-31
6 days ago
Commits (4 wk)
83
Downloads (7d)
HN mentions (30d)
Open Issues
50
Rank Change
=
was #300

Analysis

HVTrust Dimensions vs Workflow Platforms

51.7 / 100 · 100.0% confidence

LiteFlow Workflow Platforms average (23 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.8 / 25
6.6 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
1.3 below avg 12.4
Maintenance60% last-push freshness · 40% commit activity
19.3 / 20
1.1 above avg 18.2
AdoptionLog-scaled stars · package downloads
8.6 / 20
4.5 below avg 13.1

Activity Inputs

82.4 / 100
StarsRepository reach
21.5 / 30
FreshnessLast push recency
24.2 / 25
ActivityRecent commits
24.0 / 25
CommunityFork signal
12.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.0 / 10
OpenSSF Scorecard · scanned Aug 4, 2026
Signed Commits
1%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies -1
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 0

Is LiteFlow safe?

Public trust evidence for LiteFlow is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does LiteFlow publish package provenance?
No published build provenance is currently detected for LiteFlow. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does LiteFlow have an OpenSSF Scorecard?
LiteFlow has an OpenSSF Scorecard score of 3.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is LiteFlow actively maintained?
Actively maintained. The repository was pushed to within the last 6 day(s).
What license does LiteFlow use?
LiteFlow ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are LiteFlow's commits signed?
1% of the last 100 commits to LiteFlow are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain LiteFlow?

For maintainers

HVTrust scores LiteFlow from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 8Score 4HVTrust 3Listed 1Scorecard 1Grade 1
2026-07-28
Grade Changed
Trust grade D → C
2026-07-28
Rank Moved
Rank rose 42 spots (#333 → #291)
2026-07-28
HVTrust Changed
HVTrust up 6.4pts (45.8 → 52.2)
2026-07-28
Activity Score Changed
Activity score up 19pts (64 → 83)
2026-07-19
Rank Moved
Rank rose 29 spots (#355 → #326)
2026-07-19
HVTrust Changed
HVTrust up 5.0pts (41.3 → 46.3)
2026-07-19
Activity Score Changed
Activity score up 12pts (53 → 65)
2026-07-15
Rank Moved
Rank dropped 25 spots (#331 → #356)
2026-07-14
Rank Moved
Rank dropped 18 spots (#313 → #331)
2026-07-13
Rank Moved
Rank dropped 36 spots (#277 → #313)
2026-07-02
Activity Score Changed
Activity score down 6pts (61 → 55)
2026-06-30
Rank Moved
Rank dropped 12 spots (#237 → #249)
2026-06-30
Activity Score Changed
Activity score down 6pts (70 → 64)
2026-06-24
Scorecard Added
OSSF Scorecard: 3.0/10
2026-06-24
Rank Moved
Rank rose 59 spots (#294 → #235)
2026-06-24
HVTrust Changed
HVTrust up 27.8pts (21.7 → 49.5)
2026-06-23
Rank Moved
Rank dropped 11 spots (#283 → #294)
2026-06-21
Newly Listed
First tracked at rank #279

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 51.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/liteflow.svg)](https://hvtracker.net/agents/liteflow)
HTML:
<a href="https://hvtracker.net/agents/liteflow"><img src="https://hvtracker.net/badge/liteflow.svg" alt="HVTrust"></a>

Other agents in Workflow Platforms

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON