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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 2 days ago
Rank Trend
2026-06-022026-06-04
Activity & Reach
Stars
42.9k
Forks
2.9k
Last Push
2026-06-02
2 days ago
Commits (4 wk)
138
Downloads (7d)
—
HN mentions (30d)
56
Open Issues
432
Rank Change
▲97
was #183
Analysis
HVTrust Dimensions
66.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.9 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.6 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
11.1 / 20
Activity Inputs
93.6 / 100
StarsRepository reach
27.8 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
16.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.0 / 10
via deps.dev · OpenSSF
Signed Commits
68%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests10
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License9
Maintained10
Packaging-1
Pinned-Dependencies7
SAST0
Security-Policy10
Signed-Releases0
Token-Permissions0
Vulnerabilities0
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 6.0/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?
68% 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.
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 Jan?
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.
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
