ECC has an HVTrust score of 87.7/100 (Grade A), ranked #23 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for ECC?

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

ECC

affaan-m/ECC

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development f

Coding Agents JavaScript Grade A Listed MIT

87.7/100

Rank #23 of 1204

Compare ECC

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Tool Surface Changed +3

Is ECC safe? ECC scores 87.7/100 (Grade A), ranked #23 of 1204 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 5.6/10; 86% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#2 Cline — 91.3 (A) → #3 Qwen Code — 90.9 (A) → #5 Hermes Agent — 85.7 (A) → #6 Bernstein — 84.7 (A) →

Quick Trust Read

What Would Improve It

Improve safety / integrity to lift the weakest part of the trust profile.

Recent Changes

2026-08-09

Tool Surface Changed

Detected tool/plugin surface changed: declared → marketplace

2026-08-09

Provider Added

Runtime surface grew — new detected provider dependencies: Postgres, Redis

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.

Compare with Codex Get email alerts for ECC View Coding Agents Report missing data

100.0

Activity sub-score · out of 100

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 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 →

Activity & Reach

Stars

239.0k

Forks

36.3k

Last Push

2026-08-09

today

Commits (4 wk)

107

Downloads (7d)

4,560

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼9

was #14

Analysis

HVTrust Dimensions vs Coding Agents

87.7 / 100 · 100.0% confidence

ECC Coding Agents average (65 agents)

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

18.8 / 25

10.9 above avg 7.9

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.3 above avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

2.1 above avg 11.2

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

4.9 above avg 15.1

AdoptionLog-scaled stars · package downloads

17.8 / 20

5.5 above avg 12.3

Activity Inputs

100.0 / 100

StarsRepository reach

30 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

20 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.6 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

86%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 8

CII-Best-Practices 0

Code-Review 3

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 8

SAST 4

Security-Policy 4

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 6

Is ECC safe?

Public supply-chain signals for ECC are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but ECC carries less obvious unverified-evidence risk than projects with thin signals.

Does ECC publish package provenance?

Yes. ECC's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does ECC have an OpenSSF Scorecard?

ECC has an OpenSSF Scorecard score of 5.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 ECC actively maintained?

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

What license does ECC use?

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

Are ECC's commits signed?

86% of the last 100 commits to ECC 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.

Compare ECC head-to-head

ECC vs Codex → ECC vs Cline → ECC vs Qwen Code →

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

ECC appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

4 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Marketplace

Marketplace plugin/integration surface detected.

database

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 ECC'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-08-09

Tool Surface Changed

Detected tool/plugin surface changed: declared → marketplace

2026-08-09

Provider Added

Runtime surface grew — new detected provider dependencies: Postgres, Redis

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres, Redis

2026-07-28

Provenance Added

Package provenance attestation detected

2026-07-09

Provider Added

Runtime surface grew — new detected provider dependency: Redis

2026-07-04

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini, Redis, Supabase

2026-06-16

Drift Warning Cleared

Provenance drift warning cleared (now: match)

2026-06-16

Provenance Removed

Package provenance attestation no longer detected

2026-06-15

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-15

Provenance Added

Package provenance attestation detected

2026-06-13

Drift Warning Cleared

Provenance drift warning cleared (now: match)

2026-06-13

Provenance Removed

Package provenance attestation no longer detected

2026-06-11

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-11

Provenance Added

Package provenance attestation detected

2026-06-10

Drift Warning Cleared

Provenance drift warning cleared (now: match)

2026-06-10

Provenance Removed

Package provenance attestation no longer detected

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI, Postgres, Redis, Supabase

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-06-05

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-05

Provenance Added

Package provenance attestation detected

Maintain ECC?

For maintainers

HVTrust scores ECC 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-09

Tool Surface Changed

Detected tool/plugin surface changed: declared → marketplace

2026-08-09

Provider Added

Runtime surface grew — new detected provider dependencies: Postgres, Redis

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres, Redis

2026-07-28

Provenance Added

Package provenance attestation detected

2026-07-28

Grade Changed

Trust grade B → A

2026-07-28

Rank Moved

Rank rose 47 spots (#69 → #22)

2026-07-28

HVTrust Changed

HVTrust up 11.2pts (76.3 → 87.5)

2026-07-09

Provider Added

Runtime surface grew — new detected provider dependency: Redis

2026-07-04

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini, Redis, Supabase

2026-06-30

Rank Moved

Rank rose 14 spots (#78 → #64)

2026-06-16

Drift Warning Cleared

Provenance drift warning cleared (now: match)

2026-06-16

Provenance Removed

Package provenance attestation no longer detected

2026-06-16

Grade Changed

Trust grade A → B

2026-06-16

Rank Moved

Rank dropped 50 spots (#19 → #69)

2026-06-16

HVTrust Changed

HVTrust down 15.7pts (87.2 → 71.5)

2026-06-15

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-15

Provenance Added

Package provenance attestation detected

2026-06-15

Grade Changed

Trust grade B → A

2026-06-15

Rank Moved

Rank rose 43 spots (#62 → #19)

2026-06-15

HVTrust Changed

HVTrust up 14.3pts (72.9 → 87.2)

2026-06-13

Drift Warning Cleared

Provenance drift warning cleared (now: match)

2026-06-13

Provenance Removed

Package provenance attestation no longer detected

2026-06-13

Grade Changed

Trust grade A → B

2026-06-13

Rank Moved

Rank dropped 44 spots (#19 → #63)

2026-06-13

HVTrust Changed

HVTrust down 14.4pts (87.4 → 73.0)

2026-06-11

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-11

Provenance Added

Package provenance attestation detected

2026-06-11

Grade Changed

Trust grade B → A

2026-06-11

Rank Moved

Rank rose 46 spots (#64 → #18)

2026-06-11

HVTrust Changed

HVTrust up 14.5pts (73.0 → 87.5)

2026-06-10

Drift Warning Cleared

Provenance drift warning cleared (now: match)

2026-06-10

Provenance Removed

Package provenance attestation no longer detected

2026-06-10

Scorecard Added

OSSF Scorecard: 5.8/10

2026-06-10

Rank Moved

Rank dropped 18 spots (#46 → #64)

2026-06-09

Rank Moved

Rank rose 11 spots (#57 → #46)

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI, Postgres, Redis, Supabase

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-06-05

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-05

Provenance Added

Package provenance attestation detected

2026-06-04

Newly Listed

First tracked at rank #193

GitHub → npm: ecc-universal

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/ecc.svg)](https://hvtracker.net/agents/ecc)
            
HTML:
            <a href="https://hvtracker.net/agents/ecc"><img src="https://hvtracker.net/badge/ecc.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.2 · Raw JSON