Home/hermes-webui/Trust report

Trust and health report

hermes-webui - trust report

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

GraphCanon updated 2d · GitHub synced 2d · 28 views this month

Maintenance

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

Very active96% signal

last push 0d ago · last release 2d · 30 releases (90d)

+1.2k stars (30d) · +353 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 1196617276
  • Not a fork
  • Personal account
  • Computed 2d

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
11
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-537c-gmf6-5ccf
cryptography@42.0 · osv@v1
requirements.txt
GHSA-6vqw-3v5j-54x4
cryptography@42.0 · osv@v1
requirements.txt
GHSA-79v4-65xg-pq4g
cryptography@42.0 · osv@v1
requirements.txt
GHSA-9v9h-cgj8-h64p
cryptography@42.0 · osv@v1
requirements.txt
GHSA-h4gh-qq45-vh27
cryptography@42.0 · osv@v1
requirements.txt
GHSA-m959-cc7f-wv43
cryptography@42.0 · osv@v1
requirements.txt
GHSA-r6ph-v2qm-q3c2
cryptography@42.0 · osv@v1
requirements.txt
PYSEC-2024-225
cryptography@42.0 · osv@v1
requirements.txt
PYSEC-2026-1284
cryptography@42.0 · osv@v1
requirements.txt
PYSEC-2026-1285
cryptography@42.0 · osv@v1
requirements.txt
PYSEC-2026-35
cryptography@42.0 · 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/nesquena-hermes-webui/trust.

Common questions

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