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. Full methodology →
Signals refreshed2026-06-22 00:01 UTC·Repo last pushed 102 days ago
Rank Trend
2026-06-202026-06-21
Activity & Reach
Stars
9.2k
Forks
1.2k
Last Push
2026-03-12
102 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
35
Rank Change
=
was #206
Analysis
HVTrust Dimensions
43.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
6.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.2 / 17
MaintenanceFreshness and commits
5.2 / 20
AdoptionStars and downloads
9.5 / 20
Activity Inputs
49.2 / 100
StarsRepository reach
23.8 / 30
FreshnessLast push recency
10.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
14.3 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.2 / 10
OpenSSF Scorecard · scanned Jun 21, 2026
Signed Commits
50%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection0
CI-Tests0
CII-Best-Practices0
Code-Review0
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained0
Packaging10
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases8
Token-Permissions0
Vulnerabilities0
Is Chat Nio safe?
Public trust evidence for Chat Nio 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 Chat Nio publish package provenance?
No published build provenance is currently detected for Chat Nio. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Chat Nio have an OpenSSF Scorecard?
Chat Nio has an OpenSSF Scorecard score of 3.2/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 Chat Nio actively maintained?
Slowing down. Last push was 102 days ago — keep an eye on whether activity resumes.
What license does Chat Nio use?
Chat Nio ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Chat Nio's commits signed?
50% of the last 100 commits to Chat Nio 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
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Anthropic
Azure OpenAI
Google Gemini
OpenAI
Redis
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Marketplace
Marketplace plugin/integration surface detected.
code
database
search
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 Chat Nio?
HVTrust scores Chat Nio 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 v3.2 · Raw JSON
