Is Vibe Kanban safe to use?

Vibe Kanban has an HVTrust score of 44.9/100 (Grade D), ranked #529 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Vibe Kanban?

Vibe Kanban scores 44.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 27.7k GitHub stars and is categorized under Coding Agents.

Vibe Kanban

BloopAI/vibe-kanban

Get 10X more out of Claude Code, Codex or any coding agent

Coding Agents Rust Grade D Listed Apache-2.0

44.9/100

Rank #529 of 1283

Compare Vibe Kanban

How does it stack up against its Coding Agents 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-04-24 · 109d ago

Recent change

Rank +1

Is Vibe Kanban safe? Vibe Kanban scores 44.9/100 (Grade D), ranked #529 of 1283 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.8/10; 78% of recent commits are signed; last pushed 2026-04-24. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#43 opencode — 45.7 (D) → #44 Integuru — 45.0 (D) → #46 GPT Pilot — 43.5 (D) → #47 Sweep — 41.6 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-10

Rank Moved

Rank dropped 18 spots (#511 → #529)

2026-08-08

Rank Moved

Rank dropped 135 spots (#360 → #495)

2026-07-29

Scorecard Added

OSSF Scorecard: 2.8/10

Maintainer Checklist

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

Refresh maintenance signals The repo was last pushed 109 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Vibe Kanban View Coding Agents Report missing data

52.7

Activity sub-score · out of 100

#45

In Coding Agents

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 →

Activity & Reach

Stars

27.7k

Forks

3.0k

Last Push

2026-04-24

109 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

382

Rank Change

was #529

Analysis

HVTrust Dimensions vs Coding Agents

44.9 / 100 · 100.0% confidence

Vibe Kanban Coding Agents average (67 agents)

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

7.4 / 25

in line with avg 7.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

10.9 / 17

in line with avg 11.1

Maintenance60% last-push freshness · 40% commit activity

4.7 / 20

10.6 below avg 15.3

AdoptionLog-scaled stars · package downloads

10.7 / 20

1.5 below avg 12.2

Activity Inputs

52.7 / 100

StarsRepository reach

26.7 / 30

FreshnessLast push recency

9.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

16.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.8 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

78%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 1

CI-Tests 9

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 4

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Vibe Kanban safe?

Public trust evidence for Vibe Kanban 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 Vibe Kanban publish package provenance?

No published build provenance is currently detected for Vibe Kanban. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Vibe Kanban have an OpenSSF Scorecard?

Vibe Kanban has an OpenSSF Scorecard score of 2.8/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 Vibe Kanban actively maintained?

Slowing down. Last push was 109 days ago — keep an eye on whether activity resumes.

What license does Vibe Kanban use?

Vibe Kanban ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Vibe Kanban's commits signed?

78% of the last 100 commits to Vibe Kanban 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

high confidence

Implemented

Vibe Kanban appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

medium confidence

Extensions

Extension based 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

Maintain Vibe Kanban?

For maintainers

HVTrust scores Vibe Kanban 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-08-10

Rank Moved

Rank dropped 18 spots (#511 → #529)

2026-08-08

Rank Moved

Rank dropped 135 spots (#360 → #495)

2026-07-29

Scorecard Added

OSSF Scorecard: 2.8/10

2026-07-29

Rank Moved

Rank rose 85 spots (#433 → #348)

2026-07-29

HVTrust Changed

HVTrust up 25.6pts (20.2 → 45.8)

2026-07-28

Newly Listed

First tracked at rank #433

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/vibe-kanban.svg)](https://hvtracker.net/agents/vibe-kanban)
            
HTML:
            <a href="https://hvtracker.net/agents/vibe-kanban"><img src="https://hvtracker.net/badge/vibe-kanban.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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