DeepAnalyze
Website
DeepAnalyze is the first agentic LLM for autonomous data science. 🎈你的AI数据分析师，自动分析大量数据，一键生成专业分析报告！
Is DeepAnalyze safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare DeepAnalyze
How does it stack up against its Research & Data neighbours?
Pick any agent to compare →In detail: DeepAnalyze scores 21.9/100 (Grade D), ranked #1340 of 1346 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 14% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →
How DeepAnalyze 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 to 9.0no OSSF Scorecard result yet +41.1 → 63.0 C · #10 of 36
- Sign every commit14% signed today +2.2 → 24.1 D · #31 of 36
Chain of custody
Scanners check what the code says. This traces who ships DeepAnalyze 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 Partly signed
github.com/ruc-datalab/DeepAnalyze, MIT, last pushed 2026-09-23. 14% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
Published packages None
No registry package. DeepAnalyze 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 DeepAnalyze.
Evidence behind this score
Coverage D: 1 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks (missing)
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues DeepAnalyze’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 DeepAnalyze compares in Research & Data
- #31 SoL-Pi 23.2 +1.3
- #32 Agent Laboratory 23.0 +1.1
- #33 DeepAnalyze 21.9 this agent
- #34 Comp AI CRM 19.7 −2.2
- #35 ai-hedge-fund-crypto 16.2 −5.7
Bars show each HVTrust score; the tick marks DeepAnalyze’s 21.9.
Where the 21.9 comes from
HVTrust dimensions vs the Research & Data average
21.9 / 100 · 50.0% confidenceDeepAnalyze Research & Data average (36 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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
72.7 / 100Common questions about DeepAnalyze
Does DeepAnalyze publish package provenance?
Does DeepAnalyze have an OpenSSF Scorecard?
Is DeepAnalyze actively maintained?
What license does DeepAnalyze use?
Are DeepAnalyze'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.
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
Maintain DeepAnalyze?
For maintainers
HVTrust scores DeepAnalyze 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/deepanalyze)
<a href="https://hvtracker.net/agents/deepanalyze"><img src="https://hvtracker.net/badge/deepanalyze.svg" alt="HVTrust"></a>
Other agents in Research & Data
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON