updated 2026-08-23 22:32 UTC

DeepAnalyze

ruc-datalab/DeepAnalyze

DeepAnalyze is the first agentic LLM for autonomous data science. 🎈你的AI数据分析师，自动分析大量数据，一键生成专业分析报告！

Research & Data Python Grade D Listed MIT
18.3/100
Rank #1159 of 1308
Compare DeepAnalyze

How does it stack up against its Research & Data neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-07-01 · 53d ago
Recent change
Rank

Is DeepAnalyze safe? DeepAnalyze scores 18.3/100 (Grade D), ranked #1159 of 1308 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; 13% of recent commits are signed; last pushed 2026-07-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

#26 TradingAgents-astock — 19.4 (D) → #27 luxas — 19.0 (D) → #29 deep-research — 17.0 (D) → #30 InternAgent — 16.6 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-16
Rank Moved
Rank dropped 24 spots (#1132 → #1156)
2026-08-10
Rank Moved
Rank dropped 66 spots (#1060 → #1126)
2026-08-08
Rank Moved
Rank dropped 561 spots (#497 → #1058)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.
Refresh maintenance signals The repo was last pushed 53 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for DeepAnalyze View Research & Data Report missing data
52.9
Activity sub-score · out of 100
#28
In Research & Data

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 →

Signals refreshed 2026-08-23 22:32 UTC · Repo last pushed 53 days ago

Rank Trend

2026-08-11 2026-08-23

Activity & Reach

Stars
4.6k
Forks
723
Last Push
2026-07-01
53 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
16
Rank Change
▲2
was #1161

Analysis

HVTrust Dimensions vs Research & Data

18.3 / 100 · 50.0% confidence

DeepAnalyze Research & Data average (32 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.7 / 25
6.0 below avg 6.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
2.6 below avg 11.1
Maintenance60% last-push freshness · 40% commit activity
8.5 / 20
4.0 below avg 12.5
AdoptionLog-scaled stars · package downloads
8.8 / 20
2.2 below avg 11.0

Activity Inputs

52.9 / 100
StarsRepository reach
22.0 / 30
FreshnessLast push recency
17.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
13%
of last 100 commits verified

Is DeepAnalyze safe?

Public trust evidence for DeepAnalyze is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does DeepAnalyze publish package provenance?
No published build provenance is currently detected for DeepAnalyze. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does DeepAnalyze have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for DeepAnalyze. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is DeepAnalyze actively maintained?
Slowing down. Last push was 53 days ago — keep an eye on whether activity resumes.
What license does DeepAnalyze use?
DeepAnalyze ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DeepAnalyze's commits signed?
13% of the last 100 commits to DeepAnalyze 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
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
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared 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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 8Listed 1Score 1
2026-08-16
Rank Moved
Rank dropped 24 spots (#1132 → #1156)
2026-08-10
Rank Moved
Rank dropped 66 spots (#1060 → #1126)
2026-08-08
Rank Moved
Rank dropped 561 spots (#497 → #1058)
2026-08-06
Rank Moved
Rank dropped 15 spots (#454 → #469)
2026-08-03
Rank Moved
Rank dropped 17 spots (#437 → #454)
2026-07-31
Activity Score Changed
Activity score down 8pts (64 → 56)
2026-07-28
Rank Moved
Rank dropped 17 spots (#415 → #432)
2026-07-14
Rank Moved
Rank dropped 45 spots (#366 → #411)
2026-07-13
Rank Moved
Rank dropped 40 spots (#326 → #366)
2026-07-09
Newly Listed
First tracked at rank #323
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 18.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/deepanalyze.svg)](https://hvtracker.net/agents/deepanalyze)
HTML:
<a href="https://hvtracker.net/agents/deepanalyze"><img src="https://hvtracker.net/badge/deepanalyze.svg" alt="HVTrust"></a>

Other agents in Research & Data

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