updated 2026-08-06 16:30 UTC

deep-research

u14app/deep-research

Pending first signal refresh

Research & Data JavaScript Grade D Listed
14.2/100
Rank #504 of 522
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 · 49d ago
Recent change
New

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

Ranked neighbours in Research & Data

#26 InternAgent — 17.2 (D) → #27 luxas — 15.4 (D) → #29 FinnewsHunter — 14.2 (D) → #30 ai-hedge-fund-crypto — 8.8 (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-06
Newly Listed
First tracked at rank #504
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 49 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
54.3
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-06 16:30 UTC · Repo last pushed 49 days ago

Activity & Reach

Stars
4.7k
Forks
1.1k
Last Push
2026-06-18
49 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
31
Rank Change
NEW

Analysis

HVTrust Dimensions vs Research & Data

14.2 / 100 · 50.0% confidence

deep-research Research & Data average (30 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0 / 25
6.4 below avg 6.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.7 below avg 11.5
Transparency50% declared license · 50% OSSF Scorecard
0 / 17
9.4 below avg 9.4
Maintenance60% last-push freshness · 40% commit activity
8.7 / 20
3.7 below avg 12.4
AdoptionLog-scaled stars · package downloads
8.8 / 20
2.2 below avg 11.0

Activity Inputs

54.3 / 100
StarsRepository reach
22.0 / 30
FreshnessLast push recency
18.2 / 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
—
Unable to query

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 49 days ago — keep an eye on whether activity resumes.
What license does deep-research use?
deep-research ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

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
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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
Listed 1
2026-08-06
Newly Listed
First tracked at rank #504
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 14.2 Grade D
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.2 · Raw JSON