updated 2026-10-16 16:07 UTC

Open Code Review

Repository Website by alibaba

Secure, fast, efficient, battle-tested at Alibaba's scale. Hybrid architecture code review tool: deterministic pipelines + LLM Agent, precise line-level comments, built-in multi-language ruleset (NPE, thread-safety, XSS, SQL injection), OpenAI & Anthropic compatible.

Agent Skills Go Listed Apache-2.0

Is Open Code Review safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.5 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare Open Code Review

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Open Code Review scores 94.7/100 (Grade A), ranked #1 of 385 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 7.5/10; 100% of recent commits are signed; no published advisory affects its latest release (@alibaba-group/open-code-review); last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Open Code Review 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 Open Code Review and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Signed

    github.com/alibaba/open-code-review, Apache-2.0, last pushed 2026-10-16. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

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

    • Code Review10
    • Branch Protection6
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies8
    All 18 Scorecard checks
    Binary-Artifacts 9
    Branch-Protection 6
    CI-Tests 10
    CII-Best-Practices 10
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 8
    SAST 10
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 9
    Vulnerabilities 0

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @alibaba-group/open-code-review 1.13.0. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-10-13 Package provenance attestation detected
  • 2026-08-26 OSSF Scorecard: 7.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Open Code Review’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 the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Open Code Review compares in Agent Skills

  1. #1 Open Code Review 94.7 this agent
  2. #2 OmniRoute 91.9 −2.8
  3. #3 Notebooklm Py 89.8 −4.9
  4. #4 Vercel Skills 89.8 −4.9
  5. #5 Larksuite Cli 88.6 −6.1

Bars show each HVTrust score; the tick marks Open Code Review’s 94.7.

Where the 94.7 comes from

HVTrust dimensions vs the Agent Skills average

94.7 / 100 · 100.0% confidence

Open Code Review Agent Skills average (385 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
21.9 / 25
14.1 above avg 7.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.6 above avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
14.9 / 17
2.9 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.9 above avg 14.1
AdoptionLog-scaled stars · package downloads
18.0 / 20
9.0 above avg 9.0

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-10-13
Provenance Added
Package provenance attestation detected
2026-10-13
HVTrust Changed
HVTrust up 10.9pts (83.8 → 94.7)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
Maintainer Checklist
Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.
Compare with OmniRoute Get email alerts for Open Code Review View Agent Skills Report missing data
94.5
Activity sub-score · out of 100
#1
In Agent Skills

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 →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
47.5k
Forks
3.5k
Last Push
2026-10-16
today
Commits (4 wk)
98
Downloads (7d)
123,931
npm
HN mentions (30d)
—
Open Issues
132
Rank Change
=
was #1

Analysis

Activity Inputs

94.5 / 100
StarsRepository reach
28.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
24.9 / 25
CommunityFork signal
16.5 / 20

Common questions about Open Code Review

Public supply-chain signals for Open Code Review are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Open Code Review carries less obvious unverified-evidence risk than projects with thin signals.
Does Open Code Review publish package provenance?
Yes. Open Code Review's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Open Code Review have an OpenSSF Scorecard?
Open Code Review has an OpenSSF Scorecard score of 7.5/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 Open Code Review actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Open Code Review use?
Open Code Review ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Open Code Review's commits signed?
100% of the last 100 commits to Open Code Review 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 Open Code Review head-to-head

Open Code Review vs OmniRoute → Open Code Review vs Notebooklm Py → Open Code Review vs Vercel Skills →

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
Implemented
Open Code Review appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies 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
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 Open Code Review'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-10-13
Provenance Added
Package provenance attestation detected
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Open Code Review?

For maintainers

HVTrust scores Open Code Review 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
HVTrust 5Grade 4Rank 3Listed 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1Provenance 1
2026-10-13
Provenance Added
Package provenance attestation detected
2026-10-13
HVTrust Changed
HVTrust up 10.9pts (83.8 → 94.7)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 154 spots (#166 → #12)
2026-09-23
HVTrust Changed
HVTrust up 45.1pts (38.2 → 83.3)
2026-09-22
Newly Listed
First tracked at rank #166
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-05
Grade Changed
Trust grade C → A
2026-09-05
Rank Moved
Rank rose 133 spots (#139 → #6)
2026-09-05
HVTrust Changed
HVTrust up 30.1pts (52.9 → 83.0)
2026-09-03
Grade Changed
Trust grade A → C
2026-09-03
Rank Moved
Rank dropped 130 spots (#1 → #131)
2026-09-03
HVTrust Changed
HVTrust down 30.1pts (83.0 → 52.9)
2026-08-26
Scorecard Added
OSSF Scorecard: 7.8/10
2026-08-26
Grade Changed
Trust grade D → A
2026-08-26
HVTrust Changed
HVTrust up 36.7pts (46.4 → 83.1)
2026-08-11
Newly Listed
First tracked at rank #7
GitHub → Website → npm: @alibaba-group/open-code-review

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 94.7 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/open-code-review.svg)](https://hvtracker.net/agents/open-code-review)
HTML:
<a href="https://hvtracker.net/agents/open-code-review"><img src="https://hvtracker.net/badge/open-code-review.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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