Plandex

Open source AI coding agent. Designed for large projects and real world tasks.

Coding Agents Go Grade D Listed MIT
22.5/100
Rank #957 of 1308
Compare Plandex

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2025-10-03 · 320d ago
Recent change
Rank +2

Is Plandex safe? Plandex scores 22.5/100 (Grade D), ranked #957 of 1308 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.8/10; recent commits are unsigned; last pushed 2025-10-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-17
Rank Moved
Rank rose 15 spots (#966 → #951)
2026-08-16
Rank Moved
Rank dropped 26 spots (#940 → #966)
2026-08-12
Rank Moved
Rank rose 13 spots (#944 → #931)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.8/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.
Refresh maintenance signals The repo was last pushed 320 days ago. Fresh activity helps separate stable projects from stale ones.
39.5
Activity sub-score · out of 100
#65

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 →

Signals refreshed 2026-08-19 04:32 UTC · Repo last pushed 320 days ago — may be stale

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
15.6k
Forks
1.2k
Last Push
2025-10-03
320 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
39
Rank Change
▼5
was #952

Analysis

HVTrust Dimensions vs Coding Agents

22.5 / 100 · 67.0% confidence

Plandex Coding Agents average (70 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.5 / 25
4.0 below avg 7.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
10.9 / 17
in line with avg 11.1
Maintenance60% last-push freshness · 40% commit activity
0 / 20
15.3 below avg 15.3
AdoptionLog-scaled stars · package downloads
10.1 / 20
2.2 below avg 12.3

Activity Inputs

39.5 / 100
StarsRepository reach
25.2 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
14.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.8 / 10
OpenSSF Scorecard · scanned Aug 18, 2026
Signed Commits
Unable to query
Binary-Artifacts 10
Branch-Protection 3
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 6
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Plandex safe?

Public trust evidence for Plandex 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 Plandex publish package provenance?
No published build provenance is currently detected for Plandex. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Plandex have an OpenSSF Scorecard?
Plandex has an OpenSSF Scorecard score of 2.8/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 Plandex actively maintained?
Stale. The repository has not been pushed to in 320 days. Consider whether the project is still being maintained.
What license does Plandex use?
Plandex ships under MIT. 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
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
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
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • 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
Rank 16HVTrust 2Listed 1Scorecard 1
2026-08-17
Rank Moved
Rank rose 15 spots (#966 → #951)
2026-08-16
Rank Moved
Rank dropped 26 spots (#940 → #966)
2026-08-12
Rank Moved
Rank rose 13 spots (#944 → #931)
2026-08-10
Rank Moved
Rank dropped 53 spots (#885 → #938)
2026-08-08
Rank Moved
Rank dropped 406 spots (#472 → #878)
2026-08-03
Rank Moved
Rank dropped 12 spots (#432 → #444)
2026-07-28
Rank Moved
Rank dropped 15 spots (#412 → #427)
2026-07-14
Rank Moved
Rank dropped 42 spots (#365 → #407)
2026-07-13
Rank Moved
Rank dropped 40 spots (#325 → #365)
2026-06-24
Rank Moved
Rank dropped 27 spots (#288 → #315)
2026-06-23
Rank Moved
Rank dropped 17 spots (#271 → #288)
2026-06-21
Rank Moved
Rank dropped 17 spots (#251 → #268)
2026-06-20
Rank Moved
Rank dropped 23 spots (#228 → #251)
2026-06-02
Rank Moved
Rank dropped 18 spots (#177 → #195)
2026-06-01
Rank Moved
Rank dropped 10 spots (#167 → #177)
2026-05-29
HVTrust Changed
HVTrust up 6.7pts (16.1 → 22.8)
2026-05-27
Scorecard Added
OSSF Scorecard: 2.8/10
2026-05-27
HVTrust Changed
HVTrust up 6.3pts (11.1 → 17.4)
2026-05-25
Rank Moved
Rank dropped 58 spots (#88 → #146)
2026-05-24
Newly Listed
First tracked at rank #88

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 22.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/plandex.svg)](https://hvtracker.net/agents/plandex)
HTML:
<a href="https://hvtracker.net/agents/plandex"><img src="https://hvtracker.net/badge/plandex.svg" alt="HVTrust"></a>

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON