updated 2026-11-05 12:09 UTC

ByteRover CLI

Repository Website

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

Memory & Knowledge TypeScript Needs review NOASSERTION Source-available

Is ByteRover CLI safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.8 / 10
Provenance None
Signed commits 35%
Last push 133d ago
Compare ByteRover CLI

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →
Suggest a correction

In detail: ByteRover CLI scores 39.7/100 (Grade D), ranked #1212 of 1374 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.8/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 →

How ByteRover CLI could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [5.1] repository is archived

Chain of custody

Scanners check what the code says. This traces who ships ByteRover CLI and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/campfirein/byterover-cli, NOASSERTION, last pushed 2026-06-25. 35% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Oct 20, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection8
    • Signed Releasesn/a
    • Dangerous Workflow0
    • Token Permissions10
    • Pinned Dependencies1
    All 18 Scorecard checks
    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 0
    Packaging -1
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 0

  3. Published packages None

    No registry package. ByteRover CLI is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of ByteRover CLI.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues ByteRover CLI’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How ByteRover CLI compares in Memory & Knowledge

  1. #46 LightMem 48.8 +9.1
  2. #47 LLM Wiki Agent 48.0 +8.3
  3. #48 VoiceMem 42.1 +2.4
  4. #49 Memvid 41.3 +1.6
  5. #50 ByteRover CLI 39.7 this agent

Bars show each HVTrust score; the tick marks ByteRover CLI’s 39.7.

Where the 39.7 comes from

HVTrust dimensions vs the Memory & Knowledge average

39.7 / 100 · 100.0% confidence

ByteRover CLI Memory & Knowledge average (50 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.5 / 25
5.3 below avg 11.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.9 below avg 12.7
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
1.3 below avg 13.0
Maintenance60% last-push freshness · 40% commit activity
3.1 / 20
14.2 below avg 17.3
AdoptionLog-scaled stars · package downloads
8.9 / 20
4.3 below avg 13.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 12 spots (#1145 → #1157)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.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.
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 133 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[5.1] repository is archived
Compare with another agent
View Memory & Knowledge Report missing data
41.3
Activity sub-score · out of 100
#50
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 →

Signals refreshed 2026-11-05 12:09 UTC · Repo last pushed 133 days ago

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
4.9k
Forks
455
Last Push
2026-06-25
133 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
11
Rank Change
=
was #1212

Analysis

Activity Inputs

41.3 / 100
StarsRepository reach
22.2 / 30
FreshnessLast push recency
6.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.4 / 20

Common questions about ByteRover CLI

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 3.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 ByteRover CLI actively maintained?
Slowing down. Last push was 133 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
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 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-09-23
Activity Went Stale
No commits for 90 days

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
Rank 29Warning Issued 3Warning Cleared 2Stale 1
2026-10-09
Rank Moved
Rank dropped 12 spots (#1145 → #1157)
2026-10-05
Warning Issued
Warning: eligibility issues detected
2026-10-03
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-30
Warning Issued
Warning: eligibility issues detected
2026-09-29
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-28
Warning Issued
Warning: eligibility issues detected
2026-09-23
Activity Went Stale
No commits for 90 days
2026-09-23
Rank Moved
Rank dropped 630 spots (#477 → #1107)
2026-09-22
Rank Moved
Rank dropped 102 spots (#375 → #477)
2026-09-21
Rank Moved
Rank rose 727 spots (#1102 → #375)
2026-09-16
Rank Moved
Rank rose 12 spots (#1103 → #1091)
2026-09-12
Rank Moved
Rank dropped 14 spots (#1082 → #1096)
2026-09-11
Rank Moved
Rank dropped 10 spots (#1072 → #1082)
2026-09-09
Rank Moved
Rank dropped 16 spots (#1061 → #1077)
2026-09-08
Rank Moved
Rank dropped 10 spots (#1051 → #1061)
2026-09-07
Rank Moved
Rank dropped 31 spots (#1020 → #1051)
2026-09-06
Rank Moved
Rank dropped 17 spots (#1003 → #1020)
2026-09-05
Rank Moved
Rank dropped 50 spots (#953 → #1003)
2026-09-04
Rank Moved
Rank dropped 25 spots (#928 → #953)
2026-09-03
Rank Moved
Rank dropped 62 spots (#866 → #928)
2026-09-02
Rank Moved
Rank dropped 44 spots (#822 → #866)
2026-09-01
Rank Moved
Rank dropped 30 spots (#792 → #822)
2026-08-31
Rank Moved
Rank dropped 80 spots (#712 → #792)
2026-08-30
Rank Moved
Rank dropped 27 spots (#685 → #712)
2026-08-29
Rank Moved
Rank dropped 45 spots (#640 → #685)
2026-08-28
Rank Moved
Rank dropped 22 spots (#618 → #640)
2026-08-27
Rank Moved
Rank dropped 14 spots (#604 → #618)
2026-08-26
Rank Moved
Rank dropped 88 spots (#516 → #604)
2026-08-24
Rank Moved
Rank dropped 14 spots (#502 → #516)
2026-08-22
Rank Moved
Rank rose 11 spots (#517 → #506)
2026-08-19
Rank Moved
Rank dropped 12 spots (#505 → #517)
2026-08-17
Rank Moved
Rank rose 11 spots (#513 → #502)
2026-08-13
Rank Moved
Rank dropped 12 spots (#488 → #500)
2026-08-10
Rank Moved
Rank dropped 17 spots (#480 → #497)
2026-08-08
Rank Moved
Rank dropped 124 spots (#350 → #474)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 39.7 Grade D
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.4 · Raw JSON