Is deep-research safe to use?

deep-research has an HVTrust score of 17.1/100 (Grade D), ranked #1205 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for deep-research?

deep-research scores 17.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 4.7k GitHub stars and is categorized under Research & Data.

deep-research

u14app/deep-research

Use any LLMs (Large Language Models) for Deep Research. Support SSE API and MCP server.

Research & Data JavaScript Grade D Listed MIT

17.1/100

Rank #1205 of 1308

Compare deep-research

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-06-18 · 62d ago

Recent change

Rank

Is deep-research safe? deep-research scores 17.1/100 (Grade D), ranked #1205 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; 5% of recent commits are signed; last pushed 2026-06-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

#26 TradingAgents-astock — 19.3 (D) → #27 DeepAnalyze — 18.5 (D) → #29 InternAgent — 16.7 (D) → #30 luxas — 15.1 (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 25 spots (#1181 → #1206)

2026-08-10

Rank Moved

Rank dropped 70 spots (#1104 → #1174)

2026-08-08

Rank Moved

Rank dropped 597 spots (#505 → #1102)

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 62 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for deep-research View Research & Data Report missing data

52.6

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 →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

4.7k

Forks

1.1k

Last Push

2026-06-18

62 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1204

Analysis

HVTrust Dimensions vs Research & Data

17.1 / 100 · 50.0% confidence

deep-research Research & Data average (32 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

0.3 / 25

6.4 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

7.9 / 20

4.2 below avg 12.1

AdoptionLog-scaled stars · package downloads

8.8 / 20

2.2 below avg 11.0

Activity Inputs

52.6 / 100

StarsRepository reach

22.0 / 30

FreshnessLast push recency

16.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

14.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

of last 100 commits verified

Is deep-research safe?

Public trust evidence for deep-research 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 deep-research publish package provenance?

No published build provenance is currently detected for deep-research. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does deep-research have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for deep-research. 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 deep-research actively maintained?

Slowing down. Last push was 62 days ago — keep an eye on whether activity resumes.

What license does deep-research use?

deep-research ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are deep-research's commits signed?

5% of the last 100 commits to deep-research 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

high confidence

Implemented

deep-research appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

5 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool 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 deep-research?

For maintainers

HVTrust scores deep-research 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

2026-08-16

Rank Moved

Rank dropped 25 spots (#1181 → #1206)

2026-08-10

Rank Moved

Rank dropped 70 spots (#1104 → #1174)

2026-08-08

Rank Moved

Rank dropped 597 spots (#505 → #1102)

2026-08-06

Newly Listed

First tracked at rank #504

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/deep-research.svg)](https://hvtracker.net/agents/deep-research)
            
HTML:
            <a href="https://hvtracker.net/agents/deep-research"><img src="https://hvtracker.net/badge/deep-research.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