CodeWhale
Open-source Rust agent engine and terminal client for Codewhale, with provider choice, tools, approvals and receipts.
Is CodeWhale safe? Strong public trust posture, backed by multiple independent signals.
Compare CodeWhale
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: CodeWhale scores 84.2/100 (Grade A), ranked #102 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.1/10; 33% of recent commits are signed; no published advisory affects its latest release (codewhale); last pushed 2026-10-17. Every point is earned from checkable signals — never paid placement. How scoring works →
How CodeWhale 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.
- Raise the OSSF Scorecard from 6.1 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Signed-Releases 0 +6.0 → 90.2 A · #3 of 77
- Sign every commit33% signed today +3.3 → 87.5 A · #6 of 77
Chain of custody
Scanners check what the code says. This traces who ships CodeWhale and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/Hmbown/CodeWhale, MIT, last pushed 2026-10-17. 33% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 6.1/10 (scanned Oct 17, 2026). The checks that decide who can get a change released:
- Code Review1
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies4
All 18 Scorecard checks
Binary-Artifacts 9Branch-Protection 3CI-Tests 10CII-Best-Practices 0Code-Review 1Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 4SAST 8Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 8 -
Published packages Partly attested
- npm codewhale Source link points to this repo's current name Build provenance attested
-
What you install today No known advisories
Latest release checked: codewhale 0.10.1. No published advisory affects it (OSV, checked 2026-10-17).
Changes to this chain
- 2026-09-15 Package provenance attestation detected
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues CodeWhale’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.
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 CodeWhale compares in Coding Agents
- #5 Bernstein 89.1 +4.9
- #6 Hermes Agent 85.0 +0.8
- #7 CodeWhale 84.2 this agent
- #8 oh-my-pi 83.7 −0.5
- #9 Mistral Vibe 83.1 −1.1
Bars show each HVTrust score; the tick marks CodeWhale’s 84.2.
Where the 84.2 comes from
HVTrust dimensions vs the Coding Agents average
84.2 / 100 · 100.0% confidenceCodeWhale Coding Agents average (77 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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
Activity & Reach
Analysis
Activity Inputs
94.2 / 100Common questions about CodeWhale
Does CodeWhale publish package provenance?
Does CodeWhale have an OpenSSF Scorecard?
Is CodeWhale actively maintained?
What license does CodeWhale use?
Are CodeWhale's commits signed?
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.
Compare CodeWhale head-to-head
AI agent surface
MCP, providers, tool surface
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/codewhale)
<a href="https://hvtracker.net/agents/codewhale"><img src="https://hvtracker.net/badge/codewhale.svg" alt="HVTrust"></a>
Other agents in Coding Agents
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.4 · Raw JSON