Is code-mode safe to use?

code-mode has an HVTrust score of 49.7/100 (Grade D), ranked #924 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for code-mode?

code-mode scores 49.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.6k GitHub stars and is categorized under Protocols & Tool Integration.

code-mode

universal-tool-calling-protocol/code-mode

🔌 Plug-and-play library to enable agents to call MCP and UTCP tools via code execution.

Protocols & Tool Integration TypeScript Grade D Listed MPL-2.0

49.7/100

Rank #924 of 1328

Compare code-mode

How does it stack up against its Protocols & Tool Integration 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-08-25 · 26d ago

Recent change

Grade Changed

Is code-mode safe? code-mode scores 49.7/100 (Grade D), ranked #924 of 1328 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.1/10; 42% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#46 MCP Bundles — 51.3 (C) → #47 Unla — 50.3 (C) → #49 CrewAI tools — 45.9 (D) → #50 Klavis AI — 45.7 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-16

Grade Changed

Trust grade C → D

2026-09-09

Rank Moved

Rank dropped 17 spots (#885 → #902)

2026-09-07

Rank Moved

Rank dropped 44 spots (#834 → #878)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.1/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 code-mode View Protocols & Tool Integration Report missing data

58.8

Activity sub-score · out of 100

#48

In Protocols & Tool Integration

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-08-11 2026-09-20

Activity & Reach

Stars

1.6k

Forks

108

Last Push

2026-08-25

26 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #925

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

49.7 / 100 · 100.0% confidence

code-mode Protocols & Tool Integration average (61 agents)

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

6.0 / 25

4.5 below avg 10.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

11.1 / 17

1.7 below avg 12.8

Maintenance60% last-push freshness · 40% commit activity

13.1 / 20

0.9 below avg 14.0

AdoptionLog-scaled stars · package downloads

7.7 / 20

2.9 below avg 10.6

Activity Inputs

58.8 / 100

StarsRepository reach

19.2 / 30

FreshnessLast push recency

21.4 / 25

ActivityRecent commits

8.7 / 25

CommunityFork signal

9.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.1 / 10

OpenSSF Scorecard · scanned Sep 13, 2026

Signed Commits

42%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 0

CII-Best-Practices 0

Code-Review 2

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 7

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Is code-mode safe?

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

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

Does code-mode have an OpenSSF Scorecard?

code-mode has an OpenSSF Scorecard score of 3.1/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 code-mode actively maintained?

Maintained. Last push was 26 days ago.

What license does code-mode use?

code-mode ships under MPL-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are code-mode's commits signed?

41% of the last 100 commits to code-mode 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

code-mode appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool 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

Maintain code-mode?

For maintainers

HVTrust scores code-mode 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-16

Grade Changed

Trust grade C → D

2026-09-09

Rank Moved

Rank dropped 17 spots (#885 → #902)

2026-09-07

Rank Moved

Rank dropped 44 spots (#834 → #878)

2026-09-06

Rank Moved

Rank dropped 15 spots (#819 → #834)

2026-09-05

Rank Moved

Rank dropped 59 spots (#760 → #819)

2026-09-04

Rank Moved

Rank dropped 28 spots (#732 → #760)

2026-09-03

Rank Moved

Rank dropped 44 spots (#688 → #732)

2026-09-02

Scorecard Added

OSSF Scorecard: 3.1/10

2026-09-02

Grade Changed

Trust grade D → C

2026-09-02

Rank Moved

Rank rose 522 spots (#1210 → #688)

2026-09-02

HVTrust Changed

HVTrust up 28.1pts (22.7 → 50.8)

2026-09-01

Rank Moved

Rank dropped 32 spots (#1178 → #1210)

2026-08-31

Rank Moved

Rank dropped 29 spots (#1149 → #1178)

2026-08-30

Rank Moved

Rank dropped 39 spots (#1110 → #1149)

2026-08-29

Rank Moved

Rank dropped 38 spots (#1072 → #1110)

2026-08-28

Rank Moved

Rank dropped 31 spots (#1041 → #1072)

2026-08-27

Rank Moved

Rank dropped 24 spots (#1017 → #1041)

2026-08-26

Rank Moved

Rank dropped 90 spots (#927 → #1017)

2026-08-25

Rank Moved

Rank rose 192 spots (#1119 → #927)

2026-08-25

HVTrust Changed

HVTrust up 3.7pts (19.2 → 22.9)

2026-08-25

Activity Score Changed

Activity score up 18pts (44 → 62)

2026-08-24

Rank Moved

Rank dropped 12 spots (#1107 → #1119)

2026-08-16

Rank Moved

Rank dropped 28 spots (#1083 → #1111)

2026-08-10

Rank Moved

Rank dropped 62 spots (#1016 → #1078)

2026-08-08

Rank Moved

Rank dropped 516 spots (#492 → #1008)

2026-08-06

Newly Listed

First tracked at rank #508

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Protocols & Tool Integration

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.3 · Raw JSON