Home/galaxy/Trust report

Trust and health report

galaxy - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated Oct 27, 2026 · GitHub synced Oct 27, 2026

Maintenance

Snapshot computed Oct 27, 2026

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Very active96% signal

last push 0d before snapshot · last release Oct 25, 2026 · 5 releases (90d)

+27 stars (30d) · -1 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 31211061
  • Not a fork
  • GitHub organization account
  • Computed Oct 27, 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
Jul 15, 2026
Scanner
osv@v1
Published findings
12
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

MCP manifest observations

Published findings
Last query
Jul 15, 2026
Scanner
mcp_manifest@v1
Published findings
2

Static manifest observations; runtime behavior is not tested.

Dependency advisories (deduplicated)

PYSEC-2020-216
beaker@1.14.1 · osv@v1
requirements.txt
GHSA-qcq2-496w-v96p
mistune@3.2.1 · osv@v1
requirements.txt
PYSEC-2026-2210
mistune@3.2.1 · osv@v1
requirements.txt
PYSEC-2026-2211
mistune@3.2.1 · osv@v1
requirements.txt
PYSEC-2026-2212
mistune@3.2.1 · osv@v1
requirements.txt
PYSEC-2026-2213
mistune@3.2.1 · osv@v1
requirements.txt
PYSEC-2026-2214
mistune@3.2.1 · osv@v1
requirements.txt
PYSEC-2026-2215
mistune@3.2.1 · osv@v1
requirements.txt
PYSEC-2026-2216
mistune@3.2.1 · osv@v1
requirements.txt
PYSEC-2026-2217
mistune@3.2.1 · osv@v1
requirements.txt
PYSEC-2026-2218
mistune@3.2.1 · osv@v1
requirements.txt
PYSEC-2026-2652
mistune@3.2.1 · osv@v1
requirements.txt

Static MCP observations

stdio transport declared in pyproject.toml
pyproject.toml
FastMCP or MCP server entrypoint declared in pyproject.toml
pyproject.toml

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/galaxyproject-galaxy/trust.

Common questions

Is galaxy maintained?
GraphCanon rates galaxy "Very active" (96% maintenance signal from public GitHub metadata, computed Oct 27, 2026). At that snapshot, the last push was 0 days earlier. 5 GitHub releases in the 90 days preceding that snapshot. This is a recency heuristic, not a guarantee the project will stay maintained.
Is galaxy safe to use?
Last scanned Jul 15, 2026 (deps profile). Published findings: 12 low. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify galaxy as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is galaxy a fork?
No. galaxy is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does galaxy have known security vulnerabilities?
Last scanned Jul 15, 2026 (deps profile). Published findings: 12 low. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
How often is the galaxy trust report updated?
Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Oct 27, 2026 (methodology github_public_v1).
What does GraphCanon never claim about galaxy?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for galaxy. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for galaxy?
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.