updated 2026-08-15 09:02 UTC

OpenCursor

PawanOsman/OpenCursor

Open-source Cursor-like AI coding agent for VS Code — agentic chat, multi-provider LLMs (OpenAI, Ollama, llama.cpp), sem

Coding Agents TypeScript Grade C Listed MIT
56.2/100
Rank #392 of 1283
Compare OpenCursor

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-15 · 0d ago
Recent change
Rank +4

Is OpenCursor safe? OpenCursor scores 56.2/100 (Grade C), ranked #392 of 1283 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.5/10; 70% of recent commits are signed; last pushed 2026-08-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#33 Pi — 57.9 (C) → #34 Ponytail — 57.2 (C) → #36 Aider — 55.5 (C) → #37 Tabby — 52.8 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-14
Rank Moved
Rank dropped 13 spots (#387 → #400)
2026-08-13
Rank Moved
Rank dropped 14 spots (#373 → #387)
2026-08-12
Rank Moved
Rank rose 24 spots (#397 → #373)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.5/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.
Compare with another agent Get email alerts for OpenCursor View Coding Agents Report missing data
83.9
Activity sub-score · out of 100
#35
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-08-15 09:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars
6.0k
Forks
1.0k
Last Push
2026-08-15
today
Commits (4 wk)
59
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▲8
was #400

Analysis

HVTrust Dimensions vs Coding Agents

56.2 / 100 · 100.0% confidence

OpenCursor Coding Agents average (67 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.6 / 25
1.1 below avg 7.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
10.6 / 17
0.6 below avg 11.2
Maintenance60% last-push freshness · 40% commit activity
19.1 / 20
3.9 above avg 15.2
AdoptionLog-scaled stars · package downloads
9.1 / 20
3.1 below avg 12.2

Activity Inputs

83.9 / 100
StarsRepository reach
22.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
22.2 / 25
CommunityFork signal
14.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.5 / 10
OpenSSF Scorecard · scanned Aug 14, 2026
Signed Commits
70%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 6
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies -1
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions -1
Vulnerabilities 0

Is OpenCursor safe?

OpenCursor 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 OpenCursor publish package provenance?
No published build provenance is currently detected for OpenCursor. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does OpenCursor have an OpenSSF Scorecard?
OpenCursor has an OpenSSF Scorecard score of 2.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 OpenCursor actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does OpenCursor use?
OpenCursor ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenCursor's commits signed?
70% of the last 100 commits to OpenCursor 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
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 OpenCursor?

For maintainers

HVTrust scores OpenCursor 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 6Listed 1Score 1HVTrust 1Grade 1Scorecard 1
2026-08-14
Rank Moved
Rank dropped 13 spots (#387 → #400)
2026-08-13
Rank Moved
Rank dropped 14 spots (#373 → #387)
2026-08-12
Rank Moved
Rank rose 24 spots (#397 → #373)
2026-08-10
Rank Moved
Rank dropped 19 spots (#376 → #395)
2026-08-08
Rank Moved
Rank dropped 93 spots (#283 → #376)
2026-07-15
Scorecard Added
OSSF Scorecard: 3.1/10
2026-07-15
Grade Changed
Trust grade D → C
2026-07-15
Rank Moved
Rank rose 141 spots (#404 → #263)
2026-07-15
HVTrust Changed
HVTrust up 33.4pts (21.6 → 55.0)
2026-07-15
Activity Score Changed
Activity score up 13pts (66 → 79)
2026-07-14
Newly Listed
First tracked at rank #404
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/opencursor.svg)](https://hvtracker.net/agents/opencursor)
HTML:
<a href="https://hvtracker.net/agents/opencursor"><img src="https://hvtracker.net/badge/opencursor.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.3 · Raw JSON