updated 2026-08-04 02:30 UTC

KaibanJS

kaiban-ai/KaibanJS

KaibanJS is a JavaScript-native framework for building and managing multi-agent systems with a Kanban-inspired approach

Multi-Agent Systems TypeScript Grade D Listed MIT
13.1/100
Rank #465 of 468
Compare KaibanJS

How does it stack up against its Multi-Agent Systems neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-05-15 · 81d ago
Recent change
New

Is KaibanJS safe? KaibanJS scores 13.1/100 (Grade D), ranked #465 of 468 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 37% of recent commits are signed; last pushed 2026-05-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

#24 MiroFlow — 20.7 (D) → #25 swarmclaw — 18.2 (D) → #26 MassGen — 17.6 (D) → #27 GPTSwarm — 14.0 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-03
Newly Listed
First tracked at rank #465
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.
Refresh maintenance signals The repo was last pushed 81 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for KaibanJS View Multi-Agent Systems Report missing data
43.1
Activity sub-score · out of 100
#28
In Multi-Agent Systems

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

Signals refreshed 2026-08-04 02:30 UTC · Repo last pushed 81 days ago

Rank Trend

2026-08-03 2026-08-04

Activity & Reach

Stars
1.5k
Forks
157
Last Push
2026-05-15
81 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
69
Rank Change
=
was #465

Analysis

HVTrust Dimensions vs Multi-Agent Systems

13.1 / 100 · 50.0% confidence

KaibanJS Multi-Agent Systems average (28 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.8 / 25
5.3 below avg 7.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.0 below avg 11.5
Maintenance60% last-push freshness · 40% commit activity
6.6 / 20
6.1 below avg 12.7
AdoptionLog-scaled stars · package downloads
7.6 / 20
2.9 below avg 10.5

Activity Inputs

43.1 / 100
StarsRepository reach
19.0 / 30
FreshnessLast push recency
13.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
37%
of last 100 commits verified

Is KaibanJS safe?

Public trust evidence for KaibanJS 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 KaibanJS publish package provenance?
No published build provenance is currently detected for KaibanJS. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does KaibanJS have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for KaibanJS. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is KaibanJS actively maintained?
Slowing down. Last push was 81 days ago — keep an eye on whether activity resumes.
What license does KaibanJS use?
KaibanJS ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are KaibanJS's commits signed?
37% of the last 100 commits to KaibanJS 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
low confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
9 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • search
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 KaibanJS?

For maintainers

HVTrust scores KaibanJS 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1
2026-08-03
Newly Listed
First tracked at rank #465
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Multi-Agent Systems

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