updated 2026-11-05 12:09 UTC

MonkeyCode

Repository Website

企业级 AI 办公工作台

Coding Agents TypeScript Listed AGPL-3.0

Is MonkeyCode safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.7 / 10
Provenance None
Signed commits 45%
Last push today
Compare MonkeyCode

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MonkeyCode scores 57.9/100 (Grade C), ranked #764 of 1374 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.7/10; 45% of recent commits are signed; last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How MonkeyCode 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

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

  1. Source Partly signed

    github.com/chaitin/MonkeyCode, AGPL-3.0, last pushed 2026-11-05. 45% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.7/10 (scanned Nov 3, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 9
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. MonkeyCode 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-28 OSSF Scorecard: 3.7/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 MonkeyCode’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 MonkeyCode compares in Coding Agents

  1. #45 zerostack 58.8 +0.9
  2. #46 MiMo Code 58.4 +0.5
  3. #47 MonkeyCode 57.9 this agent
  4. #48 Vercel fx 57.8 −0.1
  5. #49 jcode 57.7 −0.2

Bars show each HVTrust score; the tick marks MonkeyCode’s 57.9.

Where the 57.9 comes from

HVTrust dimensions vs the Coding Agents average

57.9 / 100 · 100.0% confidence

MonkeyCode Coding Agents average (77 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.9 / 25
2.3 below avg 9.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.3 above avg 14.7
AdoptionLog-scaled stars · package downloads
8.9 / 20
3.2 below avg 12.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-02
Rank Moved
Rank rose 13 spots (#774 → #761)
2026-10-22
Rank Moved
Rank rose 14 spots (#803 → #789)
2026-10-19
Rank Moved
Rank dropped 25 spots (#770 → #795)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/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
View Coding Agents Report missing data
85.6
Activity sub-score · out of 100
#47
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 C 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 →

Signals refreshed 2026-11-05 12:09 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
5.0k
Forks
760
Last Push
2026-11-05
today
Commits (4 wk)
221
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
386
Rank Change
▼2
was #762

Analysis

Activity Inputs

85.6 / 100
StarsRepository reach
22.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.4 / 20

Common questions about MonkeyCode

MonkeyCode has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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?
MonkeyCode has an OpenSSF Scorecard score of 3.7/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 MonkeyCode actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MonkeyCode use?
MonkeyCode ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MonkeyCode's commits signed?
45% of the last 100 commits to MonkeyCode 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
medium 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 MonkeyCode'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

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
Rank 25HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1
2026-11-02
Rank Moved
Rank rose 13 spots (#774 → #761)
2026-10-22
Rank Moved
Rank rose 14 spots (#803 → #789)
2026-10-19
Rank Moved
Rank dropped 25 spots (#770 → #795)
2026-10-16
Rank Moved
Rank dropped 28 spots (#740 → #768)
2026-10-15
Rank Moved
Rank dropped 30 spots (#710 → #740)
2026-10-11
Rank Moved
Rank dropped 12 spots (#700 → #712)
2026-10-08
Rank Moved
Rank rose 13 spots (#704 → #691)
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
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 279 spots (#390 → #669)
2026-09-23
HVTrust Changed
HVTrust up 10.7pts (47.6 → 58.3)
2026-09-22
Newly Listed
First tracked at rank #390
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-07
Rank Moved
Rank dropped 39 spots (#642 → #681)
2026-09-05
Rank Moved
Rank dropped 67 spots (#570 → #637)
2026-09-04
Rank Moved
Rank dropped 17 spots (#553 → #570)
2026-09-03
Rank Moved
Rank dropped 30 spots (#523 → #553)
2026-09-02
Rank Moved
Rank dropped 18 spots (#505 → #523)
2026-08-31
Rank Moved
Rank dropped 27 spots (#474 → #501)
2026-08-30
Rank Moved
Rank rose 15 spots (#489 → #474)
2026-08-29
Rank Moved
Rank dropped 21 spots (#468 → #489)
2026-08-28
Scorecard Added
OSSF Scorecard: 3.7/10
2026-08-28
Grade Changed
Trust grade D → C
2026-08-28
Rank Moved
Rank rose 533 spots (#1001 → #468)
2026-08-28
HVTrust Changed
HVTrust up 32.1pts (23.9 → 56.0)
2026-08-27
Rank Moved
Rank dropped 32 spots (#969 → #1001)
2026-08-26
Rank Moved
Rank dropped 96 spots (#873 → #969)
2026-08-16
Rank Moved
Rank dropped 15 spots (#855 → #870)
2026-08-14
Rank Moved
Rank dropped 13 spots (#843 → #856)
2026-08-13
Rank Moved
Rank dropped 11 spots (#832 → #843)
2026-08-12
Rank Moved
Rank rose 12 spots (#844 → #832)
2026-08-10
Rank Moved
Rank dropped 45 spots (#798 → #843)
2026-08-08
Rank Moved
Rank dropped 345 spots (#448 → #793)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 57.9 Grade C
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON