Jan
Website
Jan is an open source alternative to ChatGPT that runs 100% offline on your computer.
Is Jan safe? Promising trust profile, but some evidence still deserves review.
Compare Jan
How does it stack up against its LLM Gateways & Infra neighbours?
Pick any agent to compare →In detail: Jan scores 64.2/100 (Grade C), ranked #542 of 1378 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 4.5/10; 100% of recent commits are signed; last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →
How Jan could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 4.5 to 9.0lowest checks: CII-Best-Practices 0, Dangerous-Workflow 0, Fuzzing 0 +9.4 → 73.6 B · #5 of 14
Chain of custody
Scanners check what the code says. This traces who ships Jan and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/janhq/jan, NOASSERTION, last pushed 2026-10-16. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.5/10 (scanned Oct 11, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection1
- Signed Releases0
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies5
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 1CI-Tests 10CII-Best-Practices 0Code-Review 10Contributors 10Dangerous-Workflow 0Dependency-Update-Tool 10Fuzzing 0License 9Maintained 10Packaging -1Pinned-Dependencies 5SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages None
No registry package. Jan is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Jan.
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Jan’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Jan compares in LLM Gateways & Infra
- #5 Ollama 66.4 +2.2
- #6 Instructor 64.3 +0.1
- #7 Jan 64.2 this agent
- #8 LLM Gateway 63.3 −0.9
- #9 ClawRouter 58.8 −5.4
Bars show each HVTrust score; the tick marks Jan’s 64.2.
Where the 64.2 comes from
HVTrust dimensions vs the LLM Gateways & Infra average
64.2 / 100 · 100.0% confidenceJan LLM Gateways & Infra average (14 agents)
Quick Trust Read
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. 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
94.0 / 100Common questions about Jan
Does Jan publish package provenance?
Does Jan have an OpenSSF Scorecard?
Is Jan actively maintained?
What license does Jan use?
Are Jan's commits signed?
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
AI agent surface
MCP, providers, tool surface
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/jan)
<a href="https://hvtracker.net/agents/jan"><img src="https://hvtracker.net/badge/jan.svg" alt="HVTrust"></a>
Other agents in LLM Gateways & Infra
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.4 · Raw JSON