Is GitHub Copilot CLI safe?
GitHub Copilot CLI scores 58.3/100 (Grade C), ranked #177 of 328 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 5.4/10;
19% of recent commits are signed;
last pushed 2026-07-10. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
58.3/100 · Grade C
Strongest Signal
Maintenance
15.9/20
Weakest Signal
Safety / Integrity
7.7/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
Maintainer Checklist
Declare an open licensePublish a clear OSI-approved license so usage and maintenance terms are independently verifiable.
Raise Scorecard signalsCurrent OSSF Scorecard is 5.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
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 →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed yesterday
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
10.9k
Forks
1.7k
Last Push
2026-07-10
yesterday
Commits (4 wk)
9
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1836
Rank Change
▼1
was #176
Analysis
HVTrust Dimensions
58.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
7.7 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.1 / 17
MaintenanceFreshness and commits
15.9 / 20
AdoptionStars and downloads
9.7 / 20
Activity Inputs
76.8 / 100
StarsRepository reach
24.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
12.5 / 25
CommunityFork signal
15.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.4 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
19%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests-1
CII-Best-Practices0
Code-Review0
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License9
Maintained10
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy10
Signed-Releases0
Token-Permissions9
Vulnerabilities10
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 5.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 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.
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
high confidence
Declared
Declared plugin/integration surface detected.
code
shell
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
How this surface has changed
Detected changes to GitHub Copilot CLI'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.
Detected MCP server support changed: none → implemented
Maintain GitHub Copilot CLI?
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.
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.2 · Raw JSON
