Home/open-reverselab/Trust report

Trust and health report

open-reverselab - trust report

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

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

Maintenance

Snapshot computed Oct 17, 2026

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

Very active96% signal

last push 1d before snapshot · last release Sep 7, 2026 · 2 releases (90d)

+172 stars (30d) · 0 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 1272358389
  • Not a fork
  • Personal account
  • Computed Oct 17, 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

No lockfile (source not queried)
Last query
Jul 15, 2026
Scanner
osv@v1
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

No supported MCP manifest observed in this scan
Last query
Jul 15, 2026
Scanner
mcp_manifest@v1

Static manifest observations; runtime behavior is not tested.

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/ling71671-open-reverselab/trust.

Common questions

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