Plandex
Open source AI coding agent. Designed for large projects and real world tasks.
Is Plandex safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Plandex
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: Plandex scores 23.5/100 (Grade D), ranked #1353 of 1371 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.4/10; 3% of recent commits are signed; last pushed 2025-10-03. Every point is earned from checkable signals — never paid placement. How scoring works →
How Plandex 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.4 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Dependency-Update-Tool 0 +13.9 → 37.4 D · #68 of 77
- Sign every commit3% signed today +4.9 → 28.4 D · #72 of 77
Chain of custody
Scanners check what the code says. This traces who ships Plandex 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 Partly signed
github.com/plandex-ai/plandex, MIT, last pushed 2025-10-03. 3% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 2.4/10 (scanned Oct 4, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests -1CII-Best-Practices 0Code-Review 0Contributors 6Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 0Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages None
No registry package. Plandex is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Plandex.
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 Plandex’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.
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 Plandex compares in Coding Agents
- #73 typedai 27.1 +3.6
- #74 MiniMax Code 26.7 +3.2
- #75 Devika 26.2 +2.7
- #76 Plandex 23.5 this agent
- #77 Kodu 19.6 −3.9
Bars show each HVTrust score; the tick marks Plandex’s 23.5.
Where the 23.5 comes from
HVTrust dimensions vs the Coding Agents average
23.5 / 100 · 100.0% confidencePlandex Coding Agents average (77 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
39.5 / 100Common questions about Plandex
Does Plandex publish package provenance?
Does Plandex have an OpenSSF Scorecard?
Is Plandex actively maintained?
What license does Plandex use?
Are Plandex's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Plandex?
For maintainers
HVTrust scores Plandex 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/plandex)
<a href="https://hvtracker.net/agents/plandex"><img src="https://hvtracker.net/badge/plandex.svg" alt="HVTrust"></a>
Other agents in Coding Agents
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