Is CodeWhale safe to use?

CodeWhale has an HVTrust score of 73.6/100 (Grade B), ranked #151 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for CodeWhale?

CodeWhale scores 73.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 40.9k GitHub stars and is categorized under Coding Agents.

CodeWhale

Hmbown/CodeWhale

Open-source coding agent for your terminal, built in Rust and on a journey of continuous community improvement. Issues a

Coding Agents Rust Grade B Listed MIT

73.6/100

Rank #151 of 1320

Compare CodeWhale

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-02 · 1d ago

Recent change

Provider Removed +2

Is CodeWhale safe? CodeWhale scores 73.6/100 (Grade B), ranked #151 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.0/10; 42% of recent commits are signed; last pushed 2026-09-02. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#8 OpenHands — 77.7 (B) → #9 Gemini CLI — 76.3 (B) → #11 GPTMe — 73.1 (B) → #12 DeepSeek Harness — 72.8 (B) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-02

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

2026-09-02

Rank Moved

Rank rose 39 spots (#194 → #155)

2026-08-31

Rank Moved

Rank dropped 42 spots (#149 → #191)

Maintainer Checklist

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

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

94.2

Activity sub-score · out of 100

#10

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 B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-03

Activity & Reach

Stars

40.9k

Forks

3.5k

Last Push

2026-09-02

yesterday

Commits (4 wk)

2106

Downloads (7d)

4,849

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲4

was #155

Analysis

HVTrust Dimensions vs Coding Agents

73.6 / 100 · 100.0% confidence

CodeWhale Coding Agents average (72 agents)

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

9.6 / 25

1.3 above avg 8.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

13.6 / 17

2.0 above avg 11.6

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

5.1 above avg 14.8

AdoptionLog-scaled stars · package downloads

16.0 / 20

4.0 above avg 12.0

Activity Inputs

94.2 / 100

StarsRepository reach

27.7 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

16.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.0 / 10

OpenSSF Scorecard · scanned Aug 31, 2026

Signed Commits

42%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 4

SAST 6

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 7

Is CodeWhale safe?

CodeWhale has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does CodeWhale publish package provenance?

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

Does CodeWhale have an OpenSSF Scorecard?

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

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does CodeWhale use?

CodeWhale ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are CodeWhale's commits signed?

42% of the last 100 commits to CodeWhale 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

medium 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

None detected

No clear third-party provider dependency 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

high confidence

Match

Published package metadata matches the tracked repo

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 CodeWhale'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-02

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

2026-06-16

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-06-16

Mcp Status Changed

Detected MCP server support changed: declared → implemented

Maintain CodeWhale?

For maintainers

HVTrust scores CodeWhale 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-02

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

2026-09-02

Rank Moved

Rank rose 39 spots (#194 → #155)

2026-08-31

Rank Moved

Rank dropped 42 spots (#149 → #191)

2026-08-26

Rank Moved

Rank dropped 16 spots (#125 → #141)

2026-08-23

Rank Moved

Rank rose 14 spots (#136 → #122)

2026-08-19

Rank Moved

Rank dropped 16 spots (#123 → #139)

2026-08-17

Rank Moved

Rank rose 10 spots (#134 → #124)

2026-08-14

Rank Moved

Rank dropped 13 spots (#127 → #140)

2026-08-12

Rank Moved

Rank rose 19 spots (#137 → #118)

2026-07-25

Rank Moved

Rank rose 11 spots (#107 → #96)

2026-07-23

Rank Moved

Rank rose 13 spots (#112 → #99)

2026-07-21

Rank Moved

Rank dropped 13 spots (#98 → #111)

2026-07-13

Rank Moved

Rank dropped 10 spots (#75 → #85)

2026-07-07

Rank Moved

Rank dropped 11 spots (#72 → #83)

2026-06-16

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-06-16

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-06-15

Rank Moved

Rank dropped 17 spots (#68 → #85)

2026-06-15

HVTrust Changed

HVTrust down 3.4pts (71.1 → 67.7)

2026-06-13

Rank Moved

Rank rose 13 spots (#85 → #72)

2026-06-13

HVTrust Changed

HVTrust up 3.2pts (67.9 → 71.1)

2026-06-10

Scorecard Added

OSSF Scorecard: 5.7/10

2026-06-10

Grade Changed

Trust grade D → B

2026-06-10

Rank Moved

Rank rose 99 spots (#183 → #84)

2026-06-10

HVTrust Changed

HVTrust up 30.8pts (37.5 → 68.3)

GitHub → npm: codewhale

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON