Is KaibanJS safe to use?

KaibanJS has an HVTrust score of 33.4/100 (Grade D), ranked #1266 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for KaibanJS?

KaibanJS scores 33.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.5k GitHub stars and is categorized under Multi-Agent Systems.

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

33.4/100

Rank #1266 of 1328

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 C · 2/5 signals

Last push

2026-05-15 · 126d ago

Recent change

No recent signal change

Is KaibanJS safe? KaibanJS scores 33.4/100 (Grade D), ranked #1266 of 1328 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 2.7/10; 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

#30 GPTSwarm — 37.3 (D) → #31 DeepResearchAgent — 33.4 (D) → #33 MetaGPT — 33.0 (D) → #34 WorldSeed — 32.0 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-09

Rank Moved

Rank dropped 12 spots (#1235 → #1247)

2026-09-07

Rank Moved

Rank dropped 15 spots (#1212 → #1227)

2026-09-06

Rank Moved

Rank dropped 19 spots (#1193 → #1212)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.7/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.

Refresh maintenance signals The repo was last pushed 126 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

36.8

Activity sub-score · out of 100

#32

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 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 →

Rank Trend

2026-08-11 2026-09-18

Activity & Reach

Stars

1.5k

Forks

158

Last Push

2026-05-15

126 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #1263

Analysis

HVTrust Dimensions vs Multi-Agent Systems

33.4 / 100 · 100.0% confidence

KaibanJS Multi-Agent Systems average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

5.2 / 25

3.2 below avg 8.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 11.2

Transparency50% declared license · 50% OSSF Scorecard

10.8 / 17

1.2 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

3.6 / 20

8.8 below avg 12.4

AdoptionLog-scaled stars · package downloads

7.6 / 20

2.5 below avg 10.1

Activity Inputs

36.8 / 100

StarsRepository reach

19.0 / 30

FreshnessLast push recency

7.5 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.7 / 10

OpenSSF Scorecard · scanned Sep 16, 2026

Signed Commits

37%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

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?

KaibanJS has an OpenSSF Scorecard score of 2.7/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 KaibanJS actively maintained?

Slowing down. Last push was 126 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

8 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.

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

How this surface has changed

Detected changes to KaibanJS's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-13

Activity Went Stale

No commits for 90 days

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

2026-09-09

Rank Moved

Rank dropped 12 spots (#1235 → #1247)

2026-09-07

Rank Moved

Rank dropped 15 spots (#1212 → #1227)

2026-09-06

Rank Moved

Rank dropped 19 spots (#1193 → #1212)

2026-09-05

Rank Moved

Rank dropped 30 spots (#1163 → #1193)

2026-09-04

Rank Moved

Rank dropped 16 spots (#1147 → #1163)

2026-09-03

Rank Moved

Rank dropped 46 spots (#1101 → #1147)

2026-09-02

Rank Moved

Rank dropped 45 spots (#1056 → #1101)

2026-09-01

Rank Moved

Rank dropped 40 spots (#1016 → #1056)

2026-08-31

Rank Moved

Rank dropped 36 spots (#980 → #1016)

2026-08-30

Rank Moved

Rank dropped 51 spots (#929 → #980)

2026-08-29

Rank Moved

Rank dropped 50 spots (#879 → #929)

2026-08-28

Rank Moved

Rank dropped 33 spots (#846 → #879)

2026-08-27

Rank Moved

Rank dropped 22 spots (#824 → #846)

2026-08-26

Scorecard Added

OSSF Scorecard: 2.7/10

2026-08-26

Rank Moved

Rank rose 475 spots (#1299 → #824)

2026-08-26

HVTrust Changed

HVTrust up 22.6pts (12.3 → 34.9)

2026-08-16

Rank Moved

Rank dropped 25 spots (#1271 → #1296)

2026-08-13

Activity Went Stale

No commits for 90 days

2026-08-10

Rank Moved

Rank dropped 79 spots (#1192 → #1271)

2026-08-08

Rank Moved

Rank dropped 676 spots (#516 → #1192)

2026-08-06

Rank Moved

Rank dropped 45 spots (#465 → #510)

2026-08-03

Newly Listed

First tracked at rank #465

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON