Trust and health report
onWatch - 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.
Active82% signal
last push 22d ago · last release 3w · 14 releases (90d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 1151441959
- 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-45gg-vh54-h5m9
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-5cgq-3rg8-m6cv
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-78mq-xcr3-xm33
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-89gr-r52h-f8rx
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-9m57-25v3-79x9
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-f5wc-c3c7-36mc
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-jppx-rxg9-jmrx
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-q4h4-gmj2-qvw2
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-qpw4-5x99-6vjp
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-rm3j-f69w-wqmq
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-vgwf-h737-ff37
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-w879-237q-wc7r
golang.org/x/crypto@v0.51.0 · go.sum
GHSA-x527-x647-q7gg
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5005
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5006
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5013
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5014
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5015
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5016
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5017
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5018
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5019
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5020
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5021
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5023
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5033
golang.org/x/crypto@v0.51.0 · go.sum
GO-2026-5932
golang.org/x/crypto@v0.51.0 · go.sum
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/onllm-dev-onwatch/trust.
Common questions
- Is onWatch maintained?
- GraphCanon rates onWatch "Active" (82% maintenance signal from public GitHub metadata, computed today). Last push was 22 days ago. 14 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is onWatch 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 onWatch as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is onWatch a fork?
- No. onWatch is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does onWatch 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 onWatch 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 onWatch?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for onWatch. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for onWatch?
- 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.