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. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed 2 days ago
Rank Trend
2026-05-242026-06-04
Activity & Reach
Stars
10.7k
Forks
1.6k
Last Push
2026-06-02
2 days ago
Commits (4 wk)
18
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1621
Rank Change
▼14
was #118
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
17.0 / 20
AdoptionStars and downloads
9.7 / 20
Activity Inputs
79.9 / 100
StarsRepository reach
24.2 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
15.9 / 25
CommunityFork signal
14.9 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.4 / 10
via deps.dev · OpenSSF
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 2 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
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) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
