Is Carbon Arc safe to use?

Carbon Arc has an HVTrust score of 34.4/100 (Grade D), ranked #1306 of 1387 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Carbon Arc?

Carbon Arc scores 34.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 33 GitHub stars and is categorized under MCP Servers.

Carbon Arc

Repository

Website

The infrastructure for the AI economy: primitives for inference, agents, and decisions.

MCP Servers Listed Apache-2.0

Is Carbon Arc safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.6 / 10

Provenance None

Signed commits 100%

Last push 161d ago

Compare Carbon Arc

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Carbon Arc scores 34.4/100 (Grade D), ranked #1306 of 1387 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 2.6/10; 100% of recent commits are signed; last pushed 2026-06-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How Carbon Arc 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 2.6 to 9.0lowest checks: Branch-Protection 0, CI-Tests 0, CII-Best-Practices 0 +13.4 → 47.8 D · #608 of 779

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Carbon Arc 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.

Source Signed

github.com/Carbon-Arc/mcp, Apache-2.0, last pushed 2026-06-07. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 2.6/10 (scanned Nov 15, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependenciesn/a
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10
Published packages None

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

Changes to this chain

2026-08-30 OSSF Scorecard: 2.8/10

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 Carbon Arc’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 Carbon Arc compares in MCP Servers

Bars show each HVTrust score; the tick marks Carbon Arc’s 34.4.

Where the 34.4 comes from

HVTrust dimensions vs the MCP Servers average

34.4 / 100 · 100.0% confidence

Carbon Arc MCP Servers average (779 agents)

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

8.2 / 25

2.7 below avg 10.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

10.7 / 17

1.6 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

1.3 / 20

10.9 below avg 12.2

AdoptionLog-scaled stars · package downloads

3.7 / 20

3.9 below avg 7.6

Quick Trust Read

What Would Improve It

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

Maintainer Checklist

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

Refresh maintenance signals The repo was last pushed 161 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent View MCP Servers Report missing data

12.0

Activity sub-score · out of 100

#752

In MCP Servers

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-09-29 2026-11-15

Activity & Reach

Stars

Forks

Last Push

2026-06-07

161 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #1307

Analysis

Activity Inputs

12.0 / 100

StarsRepository reach

9.2 / 30

FreshnessLast push recency

2.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

0.0 / 20

Common questions about Carbon Arc

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

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

Does Carbon Arc have an OpenSSF Scorecard?

Carbon Arc has an OpenSSF Scorecard score of 2.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 Carbon Arc actively maintained?

Slowing down. Last push was 161 days ago — keep an eye on whether activity resumes.

What license does Carbon Arc use?

Carbon Arc ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Carbon Arc's commits signed?

100% of the last 100 commits to Carbon Arc 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

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 Carbon Arc'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-05

Activity Went Stale

No commits for 90 days

Maintain Carbon Arc?

For maintainers

HVTrust scores Carbon Arc 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-10-09

Rank Moved

Rank dropped 11 spots (#1235 → #1246)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Rank Moved

Rank dropped 193 spots (#1005 → #1198)

2026-09-23

HVTrust Changed

HVTrust up 13.1pts (24.8 → 37.9)

2026-09-22

Newly Listed

First tracked at rank #1005

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 13 spots (#1170 → #1183)

2026-09-09

Rank Moved

Rank dropped 23 spots (#1147 → #1170)

2026-09-08

Rank Moved

Rank dropped 12 spots (#1135 → #1147)

2026-09-07

Rank Moved

Rank dropped 18 spots (#1117 → #1135)

2026-09-06

Rank Moved

Rank dropped 17 spots (#1100 → #1117)

2026-09-05

Activity Went Stale

No commits for 90 days

2026-09-05

Rank Moved

Rank dropped 40 spots (#1060 → #1100)

2026-09-04

Rank Moved

Rank dropped 25 spots (#1035 → #1060)

2026-09-03

Rank Moved

Rank dropped 61 spots (#974 → #1035)

2026-09-02

Rank Moved

Rank dropped 46 spots (#928 → #974)

2026-09-01

Rank Moved

Rank dropped 37 spots (#891 → #928)

2026-08-31

Rank Moved

Rank dropped 32 spots (#859 → #891)

2026-08-30

Scorecard Added

OSSF Scorecard: 2.8/10

2026-08-30

Rank Moved

Rank rose 407 spots (#1266 → #859)

2026-08-30

HVTrust Changed

HVTrust up 23.1pts (16.9 → 40.0)

2026-08-29

Rank Moved

Rank dropped 11 spots (#1255 → #1266)

2026-08-28

Rank Moved

Rank dropped 11 spots (#1244 → #1255)

2026-08-26

Rank Moved

Rank dropped 30 spots (#1206 → #1236)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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

Carbon Arc

How Carbon Arc could raise its score

Chain of custody

Source Signed

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Carbon Arc compares in MCP Servers

Where the 34.4 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Carbon Arc

AI agent surface

Maintain Carbon Arc?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers