Home/UFO/Trust report

Trust and health report

UFO - 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.

Active82% signal

last push 9d ago · last release 1w · 3 releases (90d)

+220 stars (30d) · +2 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

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
28
View source evidence

deps.dev advisories

Not queried
Scanner
deps.dev@v1
View source evidence

OpenSSF Scorecard

Not queried
Scanner
openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-3644-q5cj-c5c7
langchain@0.3.27 · osv@v1
requirements.txt
GHSA-gr75-jv2w-4656
langchain@0.3.27 · osv@v1
requirements.txt
GHSA-5xmw-vc9v-4wf2
Pillow@11.3.0 · osv@v1
requirements.txt
GHSA-cfh3-3jmp-rvhc
Pillow@11.3.0 · osv@v1
requirements.txt
GHSA-pwv6-vv43-88gr
Pillow@11.3.0 · osv@v1
requirements.txt
GHSA-r73j-pqj5-w3x7
Pillow@11.3.0 · osv@v1
requirements.txt
GHSA-whj4-6x5x-4v2j
Pillow@11.3.0 · osv@v1
requirements.txt
GHSA-wjx4-4jcj-g98j
Pillow@11.3.0 · osv@v1
requirements.txt
PYSEC-2026-165
Pillow@11.3.0 · osv@v1
requirements.txt
GHSA-4vvm-4w3v-6mr8
PyPDF2@3.0.1 · osv@v1
requirements.txt
PYSEC-2026-1835
PyPDF2@3.0.1 · osv@v1
requirements.txt
GHSA-7gcm-g887-7qv7
protobuf@4.25.8 · osv@v1
requirements.txt
PYSEC-2026-1805
protobuf@4.25.8 · osv@v1
requirements.txt
GHSA-gc5v-m9x4-r6x2
requests@2.32.5 · osv@v1
requirements.txt
GHSA-vfmq-68hx-4jfw
lxml@5.1.0 · osv@v1
requirements.txt
PYSEC-2026-87
lxml@5.1.0 · osv@v1
requirements.txt
GHSA-68rp-wp8r-4726
flask@3.0.0 · osv@v1
requirements.txt
GHSA-5h2m-4q8j-pqpj
fastmcp@2.11.3 · osv@v1
requirements.txt
GHSA-c2jp-c369-7pvx
fastmcp@2.11.3 · osv@v1
requirements.txt
GHSA-m8x7-r2rg-vh5g
fastmcp@2.11.3 · osv@v1
requirements.txt
GHSA-mxxr-jv3v-6pgc
fastmcp@2.11.3 · osv@v1
requirements.txt
GHSA-rcfx-77hg-w2wv
fastmcp@2.11.3 · osv@v1
requirements.txt
GHSA-rj5c-58rq-j5g5
fastmcp@2.11.3 · osv@v1
requirements.txt
GHSA-rww4-4w9c-7733
fastmcp@2.11.3 · osv@v1
requirements.txt
GHSA-vv7q-7jx5-f767
fastmcp@2.11.3 · osv@v1
requirements.txt
PYSEC-2026-1364
fastmcp@2.11.3 · osv@v1
requirements.txt
PYSEC-2026-1365
fastmcp@2.11.3 · osv@v1
requirements.txt
PYSEC-2026-338
fastmcp@2.11.3 · 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/microsoft-ufo/trust.

Common questions

Is UFO maintained?
GraphCanon rates UFO "Active" (82% maintenance signal from public GitHub metadata, computed 1d). Last push was 9 days ago. 3 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
Is UFO safe to use?
Last scanned 1mo (deps profile). Status: 28 low - 28 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 UFO as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is UFO a fork?
No. UFO is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does UFO have known security vulnerabilities?
Last scanned 1mo (deps profile). Status: 28 low - 28 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 UFO 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 UFO?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for UFO. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for UFO?
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.

Was this helpful?

Anonymous feedback helps us improve pages and translations.