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-04 20:15 UTC·Repo last pushed 310 days ago — may be stale
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
24.8k
Forks
2.1k
Last Push
2025-07-29
310 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
0
Open Issues
2737
Rank Change
▼6
was #176
Analysis
HVTrust Dimensions
37.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
5.6 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
10.5 / 17
MaintenanceFreshness and commits
0.0 / 20
AdoptionStars and downloads
10.5 / 20
Activity Inputs
41.9 / 100
StarsRepository reach
26.4 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
15.5 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
2.3 / 10
via deps.dev · OpenSSF
Signed Commits
55%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection0
CI-Tests0
CII-Best-Practices0
Code-Review0
Contributors10
Dangerous-Workflow-1
Dependency-Update-Tool0
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy10
Signed-Releases-1
Token-Permissions-1
Vulnerabilities0
Is JARVIS / HuggingGPT safe?
Public trust evidence for JARVIS / HuggingGPT 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 JARVIS / HuggingGPT publish package provenance?
No published build provenance is currently detected for JARVIS / HuggingGPT. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does JARVIS / HuggingGPT have an OpenSSF Scorecard?
JARVIS / HuggingGPT has an OpenSSF Scorecard score of 2.3/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 JARVIS / HuggingGPT actively maintained?
Stale. The repository has not been pushed to in 310 days. Consider whether the project is still being maintained.
What license does JARVIS / HuggingGPT use?
JARVIS / HuggingGPT ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are JARVIS / HuggingGPT's commits signed?
55% of the last 100 commits to JARVIS / HuggingGPT 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 JARVIS / HuggingGPT?
HVTrust scores JARVIS / HuggingGPT 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 · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
