Trust and health report
daily_stock_analysis - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated Sep 20, 2026 · GitHub synced Sep 20, 2026
39views this month
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Very active96% signal
last push 4d ago · last release Sep 6, 2026 · 10 releases (90d)
+2.2k stars (30d) · -2 open issues (30d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 1131513930
- Not a fork
- Personal account
- Computed Sep 18, 2026
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
- Sep 18, 2026
- Scanner
- osv@v1
- Stored findings
- 76
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-mf9w-mj56-hr94
python-dotenv@1.0.0 · osv@v1
requirements.txt
PYSEC-2026-2270
python-dotenv@1.0.0 · osv@v1
requirements.txt
GHSA-xf7x-x43h-rpqh
json-repair@0.55.1 · osv@v1
requirements.txt
GHSA-hx9q-6w63-j58v
orjson@3.10 · osv@v1
requirements.txt
PYSEC-2026-107
orjson@3.10 · osv@v1
requirements.txt
GHSA-4g5m-c9r5-49xf
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-4jcj-7x88-m979
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-4xpc-pv4p-pm3w
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-53mr-6c8q-9789
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-5jmr-gcrj-2c9q
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-69x8-hrgq-fjj8
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-6wvf-77m9-58rm
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-72m8-9m7m-h278
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-7488-6r32-c95q
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-c693-x898-5g4h
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-hx8v-g79f-8w5f
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-j37q-q7p9-vpwm
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-jjhc-v7c2-5hh6
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-m2v5-74w2-qhcj
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-mf52-j94g-746m
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-p897-vf7j-f5h8
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-qmf3-4767-5fg3
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-qrc4-49gv-mv9m
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-v4p8-mg3p-g94g
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-w2mh-qq9q-453x
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-wpfp-gwwc-vwq6
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-xqmj-j6mv-4862
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-2597
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-2598
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-2599
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-2600
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-2602
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-3476
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-3477
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-3478
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-3479
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-3861
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-388
litellm@1.80.10 · osv@v1
requirements.txt
PYSEC-2026-390
litellm@1.80.10 · osv@v1
requirements.txt
GHSA-9hjg-9r4m-mvj7
requests@2.31.0 · osv@v1
requirements.txt
GHSA-9wx4-h78v-vm56
requests@2.31.0 · osv@v1
requirements.txt
GHSA-gc5v-m9x4-r6x2
requests@2.31.0 · osv@v1
requirements.txt
PYSEC-2026-1872
requests@2.31.0 · osv@v1
requirements.txt
PYSEC-2026-1873
requests@2.31.0 · osv@v1
requirements.txt
PYSEC-2026-2275
requests@2.31.0 · osv@v1
requirements.txt
GHSA-mrfv-m5wm-5w6w
PyNaCl@1.5.0 · osv@v1
requirements.txt
PYSEC-2026-3002
PyNaCl@1.5.0 · osv@v1
requirements.txt
GHSA-cpwx-vrp4-4pq7
jinja2@3.1.0 · osv@v1
requirements.txt
GHSA-gmj6-6f8f-6699
jinja2@3.1.0 · osv@v1
requirements.txt
GHSA-h5c8-rqwp-cp95
jinja2@3.1.0 · osv@v1
requirements.txt
GHSA-h75v-3vvj-5mfj
jinja2@3.1.0 · osv@v1
requirements.txt
GHSA-q2x7-8rv6-6q7h
jinja2@3.1.0 · osv@v1
requirements.txt
PYSEC-2026-1471
jinja2@3.1.0 · osv@v1
requirements.txt
PYSEC-2026-1472
jinja2@3.1.0 · osv@v1
requirements.txt
PYSEC-2026-1473
jinja2@3.1.0 · osv@v1
requirements.txt
PYSEC-2026-1474
jinja2@3.1.0 · osv@v1
requirements.txt
PYSEC-2026-1475
jinja2@3.1.0 · osv@v1
requirements.txt
PYSEC-2024-38
fastapi@0.109.0 · osv@v1
requirements.txt
GHSA-2jv5-9r88-3w3p
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-59g5-xgcq-4qw3
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-5rvq-cxj2-64vf
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-6jv3-5f52-599m
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-mj87-hwqh-73pj
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-pp6c-gr5w-3c5g
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-v9pg-7xvm-68hf
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-vffw-93wf-4j4q
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-wp53-j4wj-2cfg
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-1850
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-1851
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-1852
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-3036
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-3037
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-3038
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-3039
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-3040
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-3041
python-multipart@0.0.6 · osv@v1
requirements.txt
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/zhulinsen-daily-stock-analysis/trust.
Common questions
- Is daily_stock_analysis maintained?
- GraphCanon rates daily_stock_analysis "Very active" (96% maintenance signal from public GitHub metadata, computed Sep 18, 2026). Last push was 4 days ago. 10 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is daily_stock_analysis safe to use?
- Last scanned Sep 18, 2026 (deps profile). Status: 76 low - 76 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 daily_stock_analysis as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is daily_stock_analysis a fork?
- No. daily_stock_analysis is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does daily_stock_analysis have known security vulnerabilities?
- Last scanned Sep 18, 2026 (deps profile). Status: 76 low - 76 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 daily_stock_analysis trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Sep 18, 2026 (methodology github_public_v1).
- What does GraphCanon never claim about daily_stock_analysis?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for daily_stock_analysis. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for daily_stock_analysis?
- 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.