Is GitHub Copilot CLI safe to use?

GitHub Copilot CLI has an HVTrust score of 60.2/100 (Grade C), ranked #328 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for GitHub Copilot CLI?

GitHub Copilot CLI scores 60.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 11.1k GitHub stars and is categorized under Coding Agents.

GitHub Copilot CLI

github/copilot-cli

GitHub Copilot CLI brings the power of Copilot coding agent directly to your terminal.

Coding Agents Shell Grade C Listed NOASSERTION Proprietary

60.2/100

Rank #328 of 1308

Compare GitHub Copilot CLI

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-24 · 1d ago

Recent change

Rank +2

Is GitHub Copilot CLI safe? GitHub Copilot CLI scores 60.2/100 (Grade C), ranked #328 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 6.0/10; 19% of recent commits are signed; last pushed 2026-08-24. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#25 Kimi Code — 60.8 (C) → #26 Superpowers — 60.7 (C) → #28 Junie — 60.0 (C) → #29 Stagewise — 59.5 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-24

Rank Moved

Rank dropped 14 spots (#312 → #326)

2026-08-22

Rank Moved

Rank rose 13 spots (#323 → #310)

2026-08-19

Rank Moved

Rank dropped 17 spots (#305 → #322)

Maintainer Checklist

Declare an open license Publish a clear OSI-approved license so usage and maintenance terms are independently verifiable.

Raise Scorecard signals Current OSSF Scorecard is 6.0/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.

Compare with another agent Get email alerts for GitHub Copilot CLI View Coding Agents Report missing data

76.5

Activity sub-score · out of 100

#27

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 →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

11.1k

Forks

1.9k

Last Push

2026-08-24

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

2163

Rank Change

▼2

was #326

Analysis

HVTrust Dimensions vs Coding Agents

60.2 / 100 · 100.0% confidence

GitHub Copilot CLI Coding Agents average (70 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.4 / 25

0.8 above avg 7.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

13.6 / 17

2.5 above avg 11.1

Maintenance60% last-push freshness · 40% commit activity

15.7 / 20

0.8 above avg 14.9

AdoptionLog-scaled stars · package downloads

9.7 / 20

2.6 below avg 12.3

Activity Inputs

76.5 / 100

StarsRepository reach

24.3 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

11.9 / 25

CommunityFork signal

15.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.0 / 10

OpenSSF Scorecard · scanned Aug 25, 2026

Signed Commits

19%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 9

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 9

Vulnerabilities 10

Is GitHub Copilot CLI safe?

Proprietary software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. GitHub Copilot CLI may have internal security practices not visible through public signals.

GitHub Copilot CLI 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 GitHub Copilot CLI publish package provenance?

No published build provenance is currently detected for GitHub Copilot CLI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does GitHub Copilot CLI have an OpenSSF Scorecard?

GitHub Copilot CLI has an OpenSSF Scorecard score of 6.0/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 GitHub Copilot CLI actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does GitHub Copilot CLI use?

GitHub Copilot CLI ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are GitHub Copilot CLI's commits signed?

19% of the last 100 commits to GitHub Copilot CLI 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

medium confidence

Implemented

GitHub Copilot CLI appears to expose MCP server capabilities.

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 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-24

Rank Moved

Rank dropped 14 spots (#312 → #326)

2026-08-22

Rank Moved

Rank rose 13 spots (#323 → #310)

2026-08-19

Rank Moved

Rank dropped 17 spots (#305 → #322)

2026-08-17

Rank Moved

Rank rose 16 spots (#327 → #311)

2026-08-16

Rank Moved

Rank dropped 10 spots (#317 → #327)

2026-08-15

Rank Moved

Rank rose 16 spots (#333 → #317)

2026-08-14

Rank Moved

Rank rose 12 spots (#345 → #333)

2026-08-13

Rank Moved

Rank dropped 19 spots (#326 → #345)

2026-08-12

Rank Moved

Rank rose 13 spots (#339 → #326)

2026-08-10

Rank Moved

Rank dropped 10 spots (#329 → #339)

2026-08-08

Rank Moved

Rank dropped 83 spots (#242 → #325)

2026-07-15

Rank Moved

Rank dropped 11 spots (#214 → #225)

2026-07-14

Rank Moved

Rank dropped 10 spots (#204 → #214)

2026-07-13

Rank Moved

Rank dropped 28 spots (#176 → #204)

2026-06-24

Rank Moved

Rank dropped 22 spots (#171 → #193)

2026-06-23

Rank Moved

Rank dropped 11 spots (#160 → #171)

2026-06-18

Rank Moved

Rank dropped 11 spots (#135 → #146)

2026-06-01

Rank Moved

Rank dropped 13 spots (#99 → #112)

2026-05-29

HVTrust Changed

HVTrust up 9.9pts (48.3 → 58.2)

2026-05-28

Activity Score Changed

Activity score up 15pts (64 → 79)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/github-copilot-cli.svg)](https://hvtracker.net/agents/github-copilot-cli)
            
HTML:
            <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

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