Is MonkeyCode safe to use?

MonkeyCode has an HVTrust score of 19.8/100 (Grade D), ranked #456 of 522 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MonkeyCode?

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

MonkeyCode

chaitin/MonkeyCode

Pending first signal refresh

Coding Agents TypeScript Grade D Listed

19.8/100

Rank #456 of 522

Compare MonkeyCode

How does it stack up against its Coding Agents 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 D · 1/5 signals

Last push

2026-08-06 · 0d ago

Recent change

New

Is MonkeyCode safe? MonkeyCode scores 19.8/100 (Grade D), ranked #456 of 522 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#57 jcode — 20.4 (D) → #58 freebuff — 20.1 (D) → #60 prime-agent — 19.6 (D) → #61 zerostack — 19.2 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-06

Newly Listed

First tracked at rank #456

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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 MonkeyCode View Coding Agents Report missing data

84.6

Activity sub-score · out of 100

#59

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

Activity & Reach

Stars

4.2k

Forks

603

Last Push

2026-08-06

today

Commits (4 wk)

646

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

163

Rank Change

NEW

Analysis

HVTrust Dimensions vs Coding Agents

19.8 / 100 · 50.0% confidence

MonkeyCode Coding Agents average (65 agents)

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

0 / 25

7.5 below avg 7.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

0 / 17

10.3 below avg 10.3

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

4.8 above avg 15.2

AdoptionLog-scaled stars · package downloads

8.7 / 20

3.6 below avg 12.3

Activity Inputs

84.6 / 100

StarsRepository reach

21.7 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

12.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

—

Unable to query

Is MonkeyCode safe?

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

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

Does MonkeyCode have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for MonkeyCode. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is MonkeyCode actively maintained?

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

What license does MonkeyCode use?

MonkeyCode ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

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

None detected

No MCP server signal detected.

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

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 MonkeyCode?

For maintainers

HVTrust scores MonkeyCode 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-06

Newly Listed

First tracked at rank #456

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON