Home/ragtune/Trust report

Trust and health report

ragtune - trust report

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

GraphCanon updated 3w · GitHub synced 3w

Maintenance

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

Slowing36% signal

last push 129d ago · last release 5mo

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 1121702246
  • Not a fork
  • Personal account
  • Computed 3w

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
62
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-6xp3-p59p-q4fj
github.com/go-pg/pg/v10@v10.11.0 · osv@v1
go.sum
GO-2025-3764
github.com/go-pg/pg/v10@v10.11.0 · osv@v1
go.sum
GHSA-9jj7-4m8r-rfcm
github.com/jackc/pgx/v5@v5.7.2 · osv@v1
go.sum
GHSA-j88v-2chj-qfwx
github.com/jackc/pgx/v5@v5.7.2 · osv@v1
go.sum
GHSA-xgrm-4fwx-7qm8
github.com/jackc/pgx/v5@v5.7.2 · osv@v1
go.sum
GO-2026-4771
github.com/jackc/pgx/v5@v5.7.2 · osv@v1
go.sum
GO-2026-4772
github.com/jackc/pgx/v5@v5.7.2 · osv@v1
go.sum
GO-2026-5004
github.com/jackc/pgx/v5@v5.7.2 · osv@v1
go.sum
GHSA-h4h6-vccr-44h2
github.com/uptrace/bun/driver/pgdriver@v1.1.12 · osv@v1
go.sum
GO-2025-3765
github.com/uptrace/bun/driver/pgdriver@v1.1.12 · osv@v1
go.sum
GHSA-45gg-vh54-h5m9
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-5cgq-3rg8-m6cv
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-78mq-xcr3-xm33
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-89gr-r52h-f8rx
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-9m57-25v3-79x9
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-f5wc-c3c7-36mc
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-f6x5-jh6r-wrfv
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-hcg3-q754-cr77
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-j5w8-q4qc-rx2x
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-jppx-rxg9-jmrx
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-q4h4-gmj2-qvw2
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-qpw4-5x99-6vjp
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-rm3j-f69w-wqmq
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-vgwf-h737-ff37
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-w879-237q-wc7r
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-x527-x647-q7gg
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2025-3487
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2025-4116
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2025-4134
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2025-4135
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5005
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5006
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5013
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5014
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5015
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5016
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5017
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5018
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5019
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5020
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5021
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5023
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5033
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GO-2026-5932
golang.org/x/crypto@v0.31.0 · osv@v1
go.sum
GHSA-5cv4-jp36-h3mw
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GHSA-qxp5-gwg8-xv66
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GHSA-vvgc-356p-c3xw
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2024-3333
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2025-3503
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2025-3595
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2026-4440
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2026-4441
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2026-4918
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2026-5025
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2026-5026
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2026-5027
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2026-5028
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2026-5029
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2026-5030
golang.org/x/net@v0.28.0 · osv@v1
go.sum
GO-2026-5024
golang.org/x/sys@v0.28.0 · osv@v1
go.sum
GHSA-p77j-4mvh-x3m3
google.golang.org/grpc@v1.66.0 · osv@v1
go.sum
GO-2026-4762
google.golang.org/grpc@v1.66.0 · osv@v1
go.sum

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/metawake-ragtune/trust.

Common questions

Is ragtune maintained?
GraphCanon rates ragtune "Slowing" (36% maintenance signal from public GitHub metadata, computed 3w). Last push was 129 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is ragtune safe to use?
Last scanned 1mo (deps profile). Status: 62 low - 62 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 ragtune as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is ragtune a fork?
No. ragtune is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does ragtune have known security vulnerabilities?
Last scanned 1mo (deps profile). Status: 62 low - 62 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 ragtune trust report updated?
Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 3w (methodology github_public_v1).
What does GraphCanon never claim about ragtune?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for ragtune. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for ragtune?
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.