GitHub Copilot CLI
GitHub Copilot CLI brings the power of Copilot coding agent directly to your terminal.
Is GitHub Copilot CLI safe? Promising trust profile, but some evidence still deserves review.
Compare GitHub Copilot CLI
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: GitHub Copilot CLI scores 63.6/100 (Grade C), ranked #544 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 7.2/10; 14% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →
How GitHub Copilot CLI 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.
- Sign every commit14% signed today +4.3 → 67.9 B · #23 of 77
- Raise the OSSF Scorecard from 7.2 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Signed-Releases 0 +3.8 → 67.4 B · #23 of 77
Chain of custody
Scanners check what the code says. This traces who ships GitHub Copilot CLI 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/github/copilot-cli, NOASSERTION, last pushed 2026-10-09. 14% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Strong
OpenSSF Scorecard rates the repository's practices 7.2/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:
- Code Review2
- Branch Protection5
- Signed Releases0
- Dangerous Workflow10
- Token Permissions9
- Pinned Dependencies10
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 5CI-Tests 6CII-Best-Practices 0Code-Review 2Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 9Maintained 10Packaging -1Pinned-Dependencies 10SAST 8Security-Policy 10Signed-Releases 0Token-Permissions 9Vulnerabilities 10 -
Published packages None
No registry package. GitHub Copilot CLI 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 GitHub Copilot CLI.
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 GitHub Copilot CLI’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 GitHub Copilot CLI compares in Coding Agents
- #26 Open SWE 65.8 +2.2
- #27 Nanocoder 64.8 +1.2
- #28 GitHub Copilot CLI 63.6 this agent
- #29 zeroshot 63.6 ±0
- #30 Archon 63.4 −0.2
Bars show each HVTrust score; the tick marks GitHub Copilot CLI’s 63.6.
Where the 63.6 comes from
HVTrust dimensions vs the Coding Agents average
63.6 / 100 · 100.0% confidenceGitHub Copilot CLI 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 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
79.6 / 100Common questions about GitHub Copilot CLI
Does GitHub Copilot CLI publish package provenance?
Does GitHub Copilot CLI have an OpenSSF Scorecard?
Is GitHub Copilot CLI actively maintained?
What license does GitHub Copilot CLI use?
Are GitHub Copilot CLI'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 GitHub Copilot CLI?
For maintainers
HVTrust scores GitHub Copilot CLI 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/github-copilot-cli)
<a href="https://hvtracker.net/agents/github-copilot-cli"><img src="https://hvtracker.net/badge/github-copilot-cli.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