Trust and health report
FEDOT - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated today · GitHub synced today
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Very active96% signal
last push 3d ago · last release 1y
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 233594133
- Not a fork
- Verified publisher: organization account
- Computed today
Security scan
Dependency advisory security scan when a lockfile is present. Not a full code audit.
- Status
- 27 low
- Last scan
- today
- Scanner
- osv@v1
Findings
GHSA-5545-2q6w-2gh6
numpy@1.16.0 · requirements.txt
GHSA-6p56-wp2h-9hxr
numpy@1.16.0 · requirements.txt
GHSA-9fq2-x9r6-wfmf
numpy@1.16.0 · requirements.txt
GHSA-f7c7-j99h-c22f
numpy@1.16.0 · requirements.txt
GHSA-fpfv-jqm9-f5jm
numpy@1.16.0 · requirements.txt
PYSEC-2019-108
numpy@1.16.0 · requirements.txt
PYSEC-2021-856
numpy@1.16.0 · requirements.txt
PYSEC-2021-857
numpy@1.16.0 · requirements.txt
GHSA-jw8x-6495-233v
scikit-learn@1.0.0 · requirements.txt
GHSA-jxfp-4rvq-9h9m
scikit-learn@1.0.0 · requirements.txt
PYSEC-2024-110
scikit-learn@1.0.0 · requirements.txt
GHSA-6hrg-qmvc-2xh8
joblib@0.17.0 · requirements.txt
PYSEC-2022-288
joblib@0.17.0 · requirements.txt
GHSA-652x-xj99-gmcc
requests@2.0 · requirements.txt
GHSA-9hjg-9r4m-mvj7
requests@2.0 · requirements.txt
GHSA-9wx4-h78v-vm56
requests@2.0 · requirements.txt
GHSA-cfj3-7x9c-4p3h
requests@2.0 · requirements.txt
GHSA-gc5v-m9x4-r6x2
requests@2.0 · requirements.txt
GHSA-x84v-xcm2-53pg
requests@2.0 · requirements.txt
PYSEC-2014-13
requests@2.0 · requirements.txt
PYSEC-2014-14
requests@2.0 · requirements.txt
PYSEC-2015-17
requests@2.0 · requirements.txt
PYSEC-2018-28
requests@2.0 · requirements.txt
PYSEC-2026-1872
requests@2.0 · requirements.txt
PYSEC-2026-1873
requests@2.0 · requirements.txt
GHSA-6w46-j5rx-g56g
pytest@6.2.0 · requirements.txt
PYSEC-2026-1845
pytest@6.2.0 · requirements.txt
Method and caveats:these are sourced, dated heuristics from public GitHub data and optional dependency scans. A status like "no criticals found on 2026-07-11" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/aimclub-fedot/trust.
Common questions
- Is FEDOT maintained?
- GraphCanon rates FEDOT "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 3 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is FEDOT safe to use?
- Last scanned today (deps profile). Status: 27 low - 27 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 FEDOT as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is FEDOT a fork?
- No. FEDOT is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does FEDOT have known security vulnerabilities?
- Last scanned today (deps profile). Status: 27 low - 27 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 FEDOT trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).
- What does GraphCanon never claim about FEDOT?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for FEDOT. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for FEDOT?
- 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.