DeepResearchAgent

DeepResearchAgent is a hierarchical multi-agent system designed not only for deep research tasks but also for general-pu

Multi-Agent Systems Python Grade D Listed MIT
35.9/100
Rank #687 of 1283
Compare DeepResearchAgent

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

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

Is DeepResearchAgent safe? DeepResearchAgent scores 35.9/100 (Grade D), ranked #687 of 1283 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 3.0/10; 3% of recent commits are signed; last pushed 2026-05-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 29 spots (#656 → #685)
2026-08-08
Rank Moved
Rank dropped 249 spots (#407 → #656)
2026-08-02
Activity Went Stale
No commits for 90 days
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/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.
Refresh maintenance signals The repo was last pushed 99 days ago. Fresh activity helps separate stable projects from stale ones.
44.8
Activity sub-score · out of 100
#20

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 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-11 21:02 UTC · Repo last pushed 99 days ago

Activity & Reach

Stars
3.5k
Forks
450
Last Push
2026-05-04
99 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
4
Rank Change
▼2
was #685

Analysis

HVTrust Dimensions vs Multi-Agent Systems

35.9 / 100 · 100.0% confidence

DeepResearchAgent Multi-Agent Systems average (35 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.9 / 25
2.3 below avg 6.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.2
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
in line with avg 11.0
Maintenance60% last-push freshness · 40% commit activity
5.4 / 20
7.6 below avg 13.0
AdoptionLog-scaled stars · package downloads
8.5 / 20
1.5 below avg 10.0

Activity Inputs

44.8 / 100
StarsRepository reach
21.3 / 30
FreshnessLast push recency
11.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.3 / 20

Supply Chain Trust

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

Is DeepResearchAgent safe?

Public trust evidence for DeepResearchAgent 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 DeepResearchAgent publish package provenance?
No published build provenance is currently detected for DeepResearchAgent. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does DeepResearchAgent have an OpenSSF Scorecard?
DeepResearchAgent has an OpenSSF Scorecard score of 3.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 DeepResearchAgent actively maintained?
Slowing down. Last push was 99 days ago — keep an eye on whether activity resumes.
What license does DeepResearchAgent use?
DeepResearchAgent ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DeepResearchAgent's commits signed?
3% of the last 100 commits to DeepResearchAgent 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
high confidence
6 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • code
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
How this surface has changed

Detected changes to DeepResearchAgent'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.

2026-08-02
Activity Went Stale
No commits for 90 days

Maintain DeepResearchAgent?

For maintainers

HVTrust scores DeepResearchAgent 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 8Listed 1HVTrust 1Scorecard 1Stale 1
2026-08-10
Rank Moved
Rank dropped 29 spots (#656 → #685)
2026-08-08
Rank Moved
Rank dropped 249 spots (#407 → #656)
2026-08-02
Activity Went Stale
No commits for 90 days
2026-07-29
Rank Moved
Rank dropped 11 spots (#382 → #393)
2026-07-15
Rank Moved
Rank dropped 25 spots (#349 → #374)
2026-07-14
Rank Moved
Rank dropped 19 spots (#330 → #349)
2026-07-13
Rank Moved
Rank dropped 37 spots (#293 → #330)
2026-06-24
Scorecard Added
OSSF Scorecard: 3.0/10
2026-06-24
Rank Moved
Rank rose 31 spots (#298 → #267)
2026-06-24
HVTrust Changed
HVTrust up 24.6pts (18.3 → 42.9)
2026-06-21
Rank Moved
Rank dropped 29 spots (#264 → #293)
2026-06-20
Newly Listed
First tracked at rank #264

Embed Badge Badge guide for maintainers →

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

Other agents in Multi-Agent Systems

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.3 · Raw JSON