DeepSeek-Reasonix

DeepSeek-native AI coding agent for your terminal. Engineered around prefix-cache stability — leave it running.

Coding Agents Go Grade C Listed MIT
60.4/100
Rank #217 of 468
Compare DeepSeek-Reasonix

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-06 · 0d ago
Recent change
Rank +1

Is DeepSeek-Reasonix safe? DeepSeek-Reasonix scores 60.4/100 (Grade C), ranked #217 of 468 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.1/10; 31% of recent commits are signed; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-02
Rank Moved
Rank dropped 16 spots (#199 → #215)
2026-07-31
Rank Moved
Rank rose 14 spots (#214 → #200)
2026-07-25
Rank Moved
Rank rose 12 spots (#220 → #208)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
92.4
Activity sub-score · out of 100
#23

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

Signals refreshed 2026-08-06 05:00 UTC · Repo last pushed today

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
31.8k
Forks
2.0k
Last Push
2026-08-06
today
Commits (4 wk)
1712
Downloads (7d)
HN mentions (30d)
Open Issues
589
Rank Change
=
was #217

Analysis

HVTrust Dimensions vs Coding Agents

60.4 / 100 · 100.0% confidence

DeepSeek-Reasonix Coding Agents average (59 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.9 / 25
in line with avg 8.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
1.5 above avg 11.3
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.3 above avg 14.7
AdoptionLog-scaled stars · package downloads
10.8 / 20
1.8 below avg 12.6

Activity Inputs

92.4 / 100
StarsRepository reach
27.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.1 / 10
OpenSSF Scorecard · scanned Aug 5, 2026
Signed Commits
31%
of last 100 commits verified
Binary-Artifacts 7
Branch-Protection 1
CI-Tests 10
CII-Best-Practices 0
Code-Review 1
Contributors 6
Dangerous-Workflow 0
Dependency-Update-Tool 10
Fuzzing 10
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 1
SAST 9
Security-Policy 4
Signed-Releases 3
Token-Permissions 0
Vulnerabilities 8

Is DeepSeek-Reasonix safe?

DeepSeek-Reasonix 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 DeepSeek-Reasonix publish package provenance?
No published build provenance is currently detected for DeepSeek-Reasonix. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does DeepSeek-Reasonix have an OpenSSF Scorecard?
DeepSeek-Reasonix has an OpenSSF Scorecard score of 5.1/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 DeepSeek-Reasonix actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does DeepSeek-Reasonix use?
DeepSeek-Reasonix ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DeepSeek-Reasonix's commits signed?
31% of the last 100 commits to DeepSeek-Reasonix 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
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • code
  • shell
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

Maintain DeepSeek-Reasonix?

For maintainers

HVTrust scores DeepSeek-Reasonix 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
Rank 11Listed 1HVTrust 1Grade 1Scorecard 1
2026-08-02
Rank Moved
Rank dropped 16 spots (#199 → #215)
2026-07-31
Rank Moved
Rank rose 14 spots (#214 → #200)
2026-07-25
Rank Moved
Rank rose 12 spots (#220 → #208)
2026-07-20
Rank Moved
Rank rose 18 spots (#226 → #208)
2026-07-15
Rank Moved
Rank dropped 13 spots (#220 → #233)
2026-07-14
Rank Moved
Rank dropped 21 spots (#199 → #220)
2026-07-13
Rank Moved
Rank dropped 26 spots (#173 → #199)
2026-06-24
Rank Moved
Rank dropped 10 spots (#159 → #169)
2026-06-23
Rank Moved
Rank dropped 12 spots (#147 → #159)
2026-06-22
Scorecard Added
OSSF Scorecard: 4.5/10
2026-06-22
Grade Changed
Trust grade D → C
2026-06-22
Rank Moved
Rank rose 108 spots (#255 → #147)
2026-06-22
HVTrust Changed
HVTrust up 35.1pts (25.6 → 60.7)
2026-06-21
Rank Moved
Rank dropped 16 spots (#239 → #255)
2026-06-20
Newly Listed
First tracked at rank #239

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 60.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/deepseek-reasonix.svg)](https://hvtracker.net/agents/deepseek-reasonix)
HTML:
<a href="https://hvtracker.net/agents/deepseek-reasonix"><img src="https://hvtracker.net/badge/deepseek-reasonix.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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