Jan has an HVTrust score of 65.7/100 (Grade B), ranked #200 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Jan?

Jan scores 65.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 43.9k GitHub stars and is categorized under LLM Gateways & Infra.

Jan

janhq/jan

Jan is an open source alternative to ChatGPT that runs 100% offline on your computer.

LLM Gateways & Infra TypeScript Grade B Listed NOASSERTION

65.7/100

Rank #200 of 1204

Compare Jan

How does it stack up against its LLM Gateways & Infra neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-07 · 2d ago

Recent change

Rank +2

Is Jan safe? Jan scores 65.7/100 (Grade B), ranked #200 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 5.8/10; 99% of recent commits are signed; last pushed 2026-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in LLM Gateways & Infra

#5 Ollama — 67.7 (B) → #6 Instructor — 67.4 (B) → #8 LLM Gateway — 62.2 (C) → #9 Portkey AI Gateway — 57.5 (C) →

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 34 spots (#162 → #196)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → extension-based

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: xAI Grok

Maintainer Checklist

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

Compare with Bifrost Get email alerts for Jan View LLM Gateways & Infra Report missing data

93.6

Activity sub-score · out of 100

In LLM Gateways & Infra

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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

43.9k

Forks

3.0k

Last Push

2026-08-07

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

129

Open Issues

356

Rank Change

▼4

was #196

Analysis

HVTrust Dimensions vs LLM Gateways & Infra

65.7 / 100 · 100.0% confidence

Jan LLM Gateways & Infra average (13 agents)

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

12.2 / 25

2.1 above avg 10.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.1 below avg 11.9

Transparency50% declared license · 50% OSSF Scorecard

13.4 / 17

1.3 above avg 12.1

Maintenance60% last-push freshness · 40% commit activity

19.8 / 20

2.5 above avg 17.3

AdoptionLog-scaled stars · package downloads

11.1 / 20

2.8 below avg 13.9

Activity Inputs

93.6 / 100

StarsRepository reach

27.9 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

24.9 / 25

CommunityFork signal

16.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.8 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

99%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 8

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 9

Maintained 10

Packaging -1

Pinned-Dependencies 6

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Jan safe?

Jan 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 Jan publish package provenance?

No published build provenance is currently detected for Jan. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Jan have an OpenSSF Scorecard?

Jan has an OpenSSF Scorecard score of 5.8/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 Jan actively maintained?

Actively maintained. The repository was pushed to within the last 2 day(s).

What license does Jan use?

Jan ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Jan's commits signed?

99% of the last 100 commits to Jan 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.

Compare Jan head-to-head

Jan vs Bifrost → Jan vs Headroom → Jan vs vLLM →

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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

3 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Extensions

Extension based plugin/integration 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 Jan'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-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → extension-based

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: xAI Grok

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintain Jan?

For maintainers

HVTrust scores Jan 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 34 spots (#162 → #196)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → extension-based

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: xAI Grok

2026-06-20

Rank Moved

Rank rose 13 spots (#103 → #90)

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-06-05

Scorecard Added

OSSF Scorecard: 6.0/10

2026-06-02

Newly Listed

First tracked at rank #183

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in LLM Gateways & Infra

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