updated 2026-10-09 08:15 UTC

GPT Pilot

Repository

The first real AI developer

Coding Agents Python Listed NOASSERTION Source-available

Is GPT Pilot safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.4 / 10
Provenance None
Signed commits 1%
Last push 113d ago
Compare GPT Pilot

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →
Suggest a correction

In detail: GPT Pilot scores 39.4/100 (Grade D), ranked #1193 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.4/10; 1% of recent commits are signed; last pushed 2026-06-18. Every point is earned from checkable signals — never paid placement. How scoring works →

How GPT Pilot 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 GPT Pilot 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.

  1. Source Partly signed

    github.com/Pythagora-io/gpt-pilot, NOASSERTION, last pushed 2026-06-18. 1% 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 2.4/10 (scanned Sep 30, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 9
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Not linked

    • PyPI gpt-pilot Source link isn't a GitHub repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of GPT Pilot.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues GPT Pilot’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 GPT Pilot compares in Coding Agents

  1. #65 Stakpak Agent 41.1 +1.7
  2. #66 RA.Aid 39.8 +0.4
  3. #67 GPT Pilot 39.4 this agent
  4. #68 Continue 33.2 −6.2
  5. #69 Sweep 32.5 −6.9

Bars show each HVTrust score; the tick marks GPT Pilot’s 39.4.

Where the 39.4 comes from

HVTrust dimensions vs the Coding Agents average

39.4 / 100 · 100.0% confidence

GPT Pilot Coding Agents average (77 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.0 / 25
5.8 below avg 8.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
10.5 / 17
1.1 below avg 11.6
Maintenance60% last-push freshness · 40% commit activity
4.5 / 20
9.9 below avg 14.4
AdoptionLog-scaled stars · package downloads
12.4 / 20
0.5 above avg 11.9

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 647 spots (#511 → #1158)
2026-09-22
Rank Moved
Rank dropped 124 spots (#387 → #511)
2026-09-21
Rank Moved
Rank rose 776 spots (#1163 → #387)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.4/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 113 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for GPT Pilot View Coding Agents Report missing data
53.1
Activity sub-score · out of 100
#67
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed 113 days ago

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
33.7k
Forks
3.5k
Last Push
2026-06-18
113 days ago
Commits (4 wk)
0
Downloads (7d)
12
pypi
HN mentions (30d)
0
Open Issues
242
Rank Change
▼1
was #1192

Analysis

Activity Inputs

53.1 / 100
StarsRepository reach
27.2 / 30
FreshnessLast push recency
9.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
16.5 / 20

Common questions about GPT Pilot

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. GPT Pilot may have internal security practices not visible through public signals.
Public trust evidence for GPT Pilot 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 GPT Pilot publish package provenance?
No published build provenance is currently detected for GPT Pilot. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does GPT Pilot have an OpenSSF Scorecard?
GPT Pilot has an OpenSSF Scorecard score of 2.4/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 GPT Pilot actively maintained?
Slowing down. Last push was 113 days ago — keep an eye on whether activity resumes.
What license does GPT Pilot use?
GPT Pilot ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are GPT Pilot's commits signed?
1% of the last 100 commits to GPT Pilot 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
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
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
How this surface has changed

Detected changes to GPT Pilot'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-16
Activity Went Stale
No commits for 90 days

Maintain GPT Pilot?

For maintainers

HVTrust scores GPT Pilot 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 26Stale 1
2026-09-23
Rank Moved
Rank dropped 647 spots (#511 → #1158)
2026-09-22
Rank Moved
Rank dropped 124 spots (#387 → #511)
2026-09-21
Rank Moved
Rank rose 776 spots (#1163 → #387)
2026-09-16
Activity Went Stale
No commits for 90 days
2026-09-13
Rank Moved
Rank dropped 11 spots (#1141 → #1152)
2026-09-12
Rank Moved
Rank dropped 11 spots (#1130 → #1141)
2026-09-08
Rank Moved
Rank dropped 10 spots (#1100 → #1110)
2026-09-07
Rank Moved
Rank dropped 26 spots (#1074 → #1100)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1060 → #1074)
2026-09-05
Rank Moved
Rank dropped 43 spots (#1017 → #1060)
2026-09-04
Rank Moved
Rank dropped 32 spots (#985 → #1017)
2026-09-03
Rank Moved
Rank dropped 53 spots (#932 → #985)
2026-09-02
Rank Moved
Rank dropped 57 spots (#875 → #932)
2026-09-01
Rank Moved
Rank dropped 34 spots (#841 → #875)
2026-08-31
Rank Moved
Rank dropped 27 spots (#814 → #841)
2026-08-30
Rank Moved
Rank dropped 30 spots (#784 → #814)
2026-08-29
Rank Moved
Rank dropped 48 spots (#736 → #784)
2026-08-28
Rank Moved
Rank dropped 27 spots (#709 → #736)
2026-08-27
Rank Moved
Rank dropped 23 spots (#686 → #709)
2026-08-26
Rank Moved
Rank dropped 96 spots (#590 → #686)
2026-08-13
Rank Moved
Rank dropped 12 spots (#552 → #564)
2026-08-10
Rank Moved
Rank dropped 18 spots (#535 → #553)
2026-08-08
Rank Moved
Rank dropped 161 spots (#374 → #535)
2026-07-29
Rank Moved
Rank dropped 11 spots (#348 → #359)
2026-07-15
Rank Moved
Rank dropped 25 spots (#311 → #336)
2026-07-14
Rank Moved
Rank dropped 21 spots (#290 → #311)
2026-07-13
Rank Moved
Rank dropped 31 spots (#259 → #290)
GitHub → PyPI: gpt-pilot

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 39.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/gpt-pilot.svg)](https://hvtracker.net/agents/gpt-pilot)
HTML:
<a href="https://hvtracker.net/agents/gpt-pilot"><img src="https://hvtracker.net/badge/gpt-pilot.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 · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON