Trust and health report
deep-research - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 1d · GitHub synced 1d
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Slowing36% signal
last push 129d ago
+195 stars (30d) · +3 open issues (30d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 926861272
- Not a fork
- Personal account
- Computed 1d
Security intelligence
Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.
OSV dependency advisories
Published findings- Last query
- 1mo
- Scanner
- osv@v1
- Stored findings
- 39
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-866g-f22w-33x8
@ai-sdk/provider-utils@2.1.11 · osv@v1
package-lock.json
GHSA-rwvc-j5jr-mgvh
ai@4.1.17 · osv@v1
package-lock.json
GHSA-35jp-ww65-95wh
axios@1.7.9 · osv@v1
package-lock.json
GHSA-3g43-6gmg-66jw
axios@1.7.9 · osv@v1
package-lock.json
GHSA-3p68-rc4w-qgx5
axios@1.7.9 · osv@v1
package-lock.json
GHSA-3w6x-2g7m-8v23
axios@1.7.9 · osv@v1
package-lock.json
GHSA-43fc-jf86-j433
axios@1.7.9 · osv@v1
package-lock.json
GHSA-445q-vr5w-6q77
axios@1.7.9 · osv@v1
package-lock.json
GHSA-4hjh-wcwx-xvwj
axios@1.7.9 · osv@v1
package-lock.json
GHSA-5c9x-8gcm-mpgx
axios@1.7.9 · osv@v1
package-lock.json
GHSA-62hf-57xw-28j9
axios@1.7.9 · osv@v1
package-lock.json
GHSA-6chq-wfr3-2hj9
axios@1.7.9 · osv@v1
package-lock.json
GHSA-777c-7fjr-54vf
axios@1.7.9 · osv@v1
package-lock.json
GHSA-898c-q2cr-xwhg
axios@1.7.9 · osv@v1
package-lock.json
GHSA-fvcv-3m26-pcqx
axios@1.7.9 · osv@v1
package-lock.json
GHSA-hfxv-24rg-xrqf
axios@1.7.9 · osv@v1
package-lock.json
GHSA-j5f8-grm9-p9fc
axios@1.7.9 · osv@v1
package-lock.json
GHSA-jr5f-v2jv-69x6
axios@1.7.9 · osv@v1
package-lock.json
GHSA-m7pr-hjqh-92cm
axios@1.7.9 · osv@v1
package-lock.json
GHSA-p92q-9vqr-4j8v
axios@1.7.9 · osv@v1
package-lock.json
GHSA-pf86-5x62-jrwf
axios@1.7.9 · osv@v1
package-lock.json
GHSA-pmwg-cvhr-8vh7
axios@1.7.9 · osv@v1
package-lock.json
GHSA-q8qp-cvcw-x6jj
axios@1.7.9 · osv@v1
package-lock.json
GHSA-vf2m-468p-8v99
axios@1.7.9 · osv@v1
package-lock.json
GHSA-w9j2-pvgh-6h63
axios@1.7.9 · osv@v1
package-lock.json
GHSA-xhjh-pmcv-23jw
axios@1.7.9 · osv@v1
package-lock.json
GHSA-xx6v-rp6x-q39c
axios@1.7.9 · osv@v1
package-lock.json
GHSA-67mh-4wv8-2f99
esbuild@0.23.1 · osv@v1
package-lock.json
GHSA-r4q5-vmmm-2653
follow-redirects@1.15.9 · osv@v1
package-lock.json
GHSA-fjxv-7rqg-78g4
form-data@4.0.1 · osv@v1
package-lock.json
GHSA-hmw2-7cc7-3qxx
form-data@4.0.1 · osv@v1
package-lock.json
GHSA-33vc-wfww-vjfv
jsondiffpatch@0.6.0 · osv@v1
package-lock.json
GHSA-f23m-r3pf-42rh
lodash-es@4.17.21 · osv@v1
package-lock.json
GHSA-r5fr-rjxr-66jc
lodash-es@4.17.21 · osv@v1
package-lock.json
GHSA-xxjr-mmjv-4gpg
lodash-es@4.17.21 · osv@v1
package-lock.json
GHSA-37ch-88jc-xwx2
path-to-regexp@0.1.12 · osv@v1
package-lock.json
GHSA-6rw7-vpxm-498p
qs@6.13.0 · osv@v1
package-lock.json
GHSA-q8mj-m7cp-5q26
qs@6.13.0 · osv@v1
package-lock.json
GHSA-w7fw-mjwx-w883
qs@6.13.0 · osv@v1
package-lock.json
Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/dzhng-deep-research/trust.
Common questions
- Is deep-research maintained?
- GraphCanon rates deep-research "Slowing" (36% maintenance signal from public GitHub metadata, computed 1d). Last push was 129 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is deep-research safe to use?
- Last scanned 1mo (deps profile). Status: 39 low - 39 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify deep-research as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is deep-research a fork?
- No. deep-research is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does deep-research have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 39 low - 39 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
- How often is the deep-research trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 1d (methodology github_public_v1).
- What does GraphCanon never claim about deep-research?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for deep-research. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for deep-research?
- Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.