Is JARVIS / HuggingGPT safe to use?

JARVIS / HuggingGPT has an HVTrust score of 26.5/100 (Grade D), ranked #756 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for JARVIS / HuggingGPT?

JARVIS / HuggingGPT scores 26.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 25.1k GitHub stars and is categorized under Agent Frameworks.

JARVIS / HuggingGPT

microsoft/JARVIS

JARVIS, a system to connect LLMs with ML community. Paper: https://arxiv.org/pdf/2303.17580.pdf

Agent Frameworks Python Grade D Needs review MIT

26.5/100

Rank #756 of 1204

Compare JARVIS / HuggingGPT

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Needs review

Evidence coverage

Grade B · 3/5 signals

Last push

2025-07-29 · 376d ago

Recent change

Rank

Is JARVIS / HuggingGPT safe? JARVIS / HuggingGPT scores 26.5/100 (Grade D), ranked #756 of 1204 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.3/10; 55% of recent commits are signed; last pushed 2025-07-29. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#84 AutoAgent — 30.4 (D) → #85 BabyAGI — 30.2 (D) → #87 aeon — 26.1 (D) → #88 AIlice — 25.7 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-08

Rank Moved

Rank dropped 323 spots (#429 → #752)

2026-07-30

Rank Moved

Rank dropped 26 spots (#396 → #422)

2026-07-30

HVTrust Changed

HVTrust down 10.0pts (36.2 → 26.2)

Maintainer Checklist

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

Refresh maintenance signals The repo was last pushed 376 days ago. Fresh activity helps separate stable projects from stale ones.

Review Flags

[4.2.1] no meaningful activity in 12 months (last push 2025-07-29)

Compare with another agent Get email alerts for JARVIS / HuggingGPT View Agent Frameworks Report missing data

41.9

Activity sub-score · out of 100

#86

In Agent Frameworks

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. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

25.1k

Forks

2.2k

Last Push

2025-07-29

376 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

Open Issues

3859

Rank Change

▼4

was #752

Analysis

HVTrust Dimensions vs Agent Frameworks

26.5 / 100 · 100.0% confidence

JARVIS / HuggingGPT Agent Frameworks average (117 agents)

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

5.6 / 25

2.6 below avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

10.5 / 17

1.1 below avg 11.6

Maintenance60% last-push freshness · 40% commit activity

0 / 20

14.3 below avg 14.3

AdoptionLog-scaled stars · package downloads

10.6 / 20

0.8 below avg 11.4

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

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

55%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

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

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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

OpenAI

Credential signal: API keys or service config markers documented.

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

How this surface has changed

Detected changes to JARVIS / HuggingGPT'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.

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

Maintain JARVIS / HuggingGPT?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-08

Rank Moved

Rank dropped 323 spots (#429 → #752)

2026-07-30

Rank Moved

Rank dropped 26 spots (#396 → #422)

2026-07-30

HVTrust Changed

HVTrust down 10.0pts (36.2 → 26.2)

2026-07-29

Warning Issued

Warning: eligibility issues detected

2026-07-29

Rank Moved

Rank dropped 11 spots (#385 → #396)

2026-07-15

Rank Moved

Rank dropped 25 spots (#357 → #382)

2026-07-14

Rank Moved

Rank dropped 20 spots (#337 → #357)

2026-07-13

Rank Moved

Rank dropped 36 spots (#301 → #337)

2026-06-24

Rank Moved

Rank dropped 35 spots (#261 → #296)

2026-06-23

Rank Moved

Rank dropped 21 spots (#240 → #261)

2026-06-22

Rank Moved

Rank dropped 11 spots (#229 → #240)

2026-06-21

Rank Moved

Rank dropped 14 spots (#215 → #229)

2026-06-10

Rank Moved

Rank dropped 10 spots (#185 → #195)

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-06-02

Rank Moved

Rank dropped 14 spots (#162 → #176)

2026-06-01

Rank Moved

Rank dropped 19 spots (#143 → #162)

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (26.4 → 36.4)

2026-05-27

Scorecard Added

OSSF Scorecard: 2.3/10

2026-05-27

Grade Changed

Trust grade D → C

2026-05-27

HVTrust Changed

HVTrust up 10.8pts (11.5 → 22.3)

2026-05-25

Newly Listed

First tracked at rank #143

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/jarvis-hugginggpt.svg)](https://hvtracker.net/agents/jarvis-hugginggpt)
            
HTML:
            <a href="https://hvtracker.net/agents/jarvis-hugginggpt"><img src="https://hvtracker.net/badge/jarvis-hugginggpt.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON