Is ByteRover CLI safe to use?

ByteRover CLI has an HVTrust score of 47.5/100 (Grade D), ranked #333 of 468 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for ByteRover CLI?

ByteRover CLI scores 47.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 4.9k GitHub stars and is categorized under Memory & Knowledge.

ByteRover CLI

campfirein/byterover-cli

ByteRover CLI (brv) - The portable memory layer for autonomous coding agents (formerly Cipher)

Memory & Knowledge TypeScript Grade D Listed NOASSERTION Source-available

47.5/100

Rank #333 of 468

Compare ByteRover CLI

How does it stack up against its Memory & Knowledge 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-06-25 · 42d ago

Recent change

No recent signal change

Is ByteRover CLI safe? ByteRover CLI scores 47.5/100 (Grade D), ranked #333 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 4.6/10; 35% of recent commits are signed; last pushed 2026-06-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#30 LycheeMemory — 49.6 (D) → #31 LightMem — 49.6 (D) → #33 EverOS — 46.7 (D) → #34 AnythingLLM — 43.4 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-07-29

Rank Moved

Rank dropped 11 spots (#319 → #330)

2026-07-25

Rank Moved

Rank dropped 10 spots (#303 → #313)

2026-07-19

Grade Changed

Trust grade C → D

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.6/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 42 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for ByteRover CLI View Memory & Knowledge Report missing data

53.9

Activity sub-score · out of 100

#32

In Memory & Knowledge

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-07-05 2026-08-06

Activity & Reach

Stars

4.9k

Forks

452

Last Push

2026-06-25

42 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #333

Analysis

HVTrust Dimensions vs Memory & Knowledge

47.5 / 100 · 100.0% confidence

ByteRover CLI Memory & Knowledge average (37 agents)

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

7.5 / 25

3.0 below avg 10.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.6 below avg 12.4

Transparency50% declared license · 50% OSSF Scorecard

12.4 / 17

in line with avg 12.6

Maintenance60% last-push freshness · 40% commit activity

9.2 / 20

8.4 below avg 17.6

AdoptionLog-scaled stars · package downloads

8.9 / 20

5.3 below avg 14.2

Activity Inputs

53.9 / 100

StarsRepository reach

22.2 / 30

FreshnessLast push recency

19.2 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

12.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.6 / 10

OpenSSF Scorecard · scanned Jul 11, 2026 (refresh pending)

Signed Commits

35%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 9

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 0

Fuzzing 0

License 9

Maintained 10

Packaging -1

Pinned-Dependencies 1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0

Is ByteRover CLI safe?

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. ByteRover CLI may have internal security practices not visible through public signals.

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

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

Does ByteRover CLI have an OpenSSF Scorecard?

ByteRover CLI has an OpenSSF Scorecard score of 4.6/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 ByteRover CLI actively maintained?

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

What license does ByteRover CLI use?

ByteRover CLI ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are ByteRover CLI's commits signed?

35% of the last 100 commits to ByteRover CLI 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

ByteRover CLI appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

7 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium 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 ByteRover CLI'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-07-17

Provider Added

Runtime surface grew — new detected provider dependencies: Cohere, Google Gemini, Groq, OpenRouter, xAI Grok

2026-07-04

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini

Maintain ByteRover CLI?

For maintainers

HVTrust scores ByteRover CLI 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-07-29

Rank Moved

Rank dropped 11 spots (#319 → #330)

2026-07-25

Rank Moved

Rank dropped 10 spots (#303 → #313)

2026-07-19

Grade Changed

Trust grade C → D

2026-07-17

Provider Added

Runtime surface grew — new detected provider dependencies: Cohere, Google Gemini, Groq, OpenRouter, xAI Grok

2026-07-17

Rank Moved

Rank dropped 21 spots (#279 → #300)

2026-07-15

Rank Moved

Rank dropped 14 spots (#264 → #278)

2026-07-14

Rank Moved

Rank dropped 17 spots (#247 → #264)

2026-07-13

Rank Moved

Rank dropped 28 spots (#219 → #247)

2026-07-04

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini

2026-07-02

Activity Score Changed

Activity score down 5pts (67 → 62)

2026-06-28

Rank Moved

Rank dropped 18 spots (#199 → #217)

2026-06-28

HVTrust Changed

HVTrust down 3.3pts (56.7 → 53.4)

2026-06-24

Scorecard Added

OSSF Scorecard: 4.6/10

2026-06-24

Grade Changed

Trust grade D → C

2026-06-24

Rank Moved

Rank rose 94 spots (#286 → #192)

2026-06-24

HVTrust Changed

HVTrust up 33.4pts (24.3 → 57.7)

2026-06-23

Activity Score Changed

Activity score up 14pts (68 → 81)

2026-06-21

Rank Moved

Rank dropped 33 spots (#249 → #282)

2026-06-21

Activity Score Changed

Activity score down 12pts (79 → 68)

2026-06-20

Newly Listed

First tracked at rank #249

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Memory & Knowledge

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