Is rulego maintained?

GraphCanon rates rulego "Very active" (96% maintenance signal from public GitHub metadata, computed Sep 20, 2026). Last push was 5 days ago. 1 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

Is rulego safe to use?

Last scanned Sep 6, 2026 (deps profile). Status: 63 low - 63 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 rulego as safe - review maintenance, provenance, and scan findings on this page before adopting.

No. rulego is not flagged as a fork in GitHub metadata at the time of the last refresh.

Does rulego have known security vulnerabilities?

Last scanned Sep 6, 2026 (deps profile). Status: 63 low - 63 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 rulego trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Sep 20, 2026 (methodology github_public_v1).

What does GraphCanon never claim about rulego?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for rulego. Signals are sourced heuristics with explicit limits - see trust methodology (https://www.graphcanon.com/trust-methodology).

How does GraphCanon assess trust for rulego?

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 (https://www.graphcanon.com/trust-methodology) for full scope and limits.

Home/rulego/Trust report

Trust and health report

rulego - trust report

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

GraphCanon updated Sep 20, 2026 · GitHub synced Sep 20, 2026

30views this month

Maintenance

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

Very active96% signal

last push 5d ago · last release Aug 3, 2026 · 1 releases (90d)

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

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 669830822
Not a fork
Verified publisher: organization account
Computed Sep 20, 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: Sep 6, 2026
Scanner: osv@v1
Stored findings: 63

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-fw7p-63qq-7hpr

filippo.io/edwards25519@v1.1.0 · osv@v1

go.sum

GO-2026-4503

filippo.io/edwards25519@v1.1.0 · osv@v1

go.sum

GHSA-32fw-gq77-f2f2

github.com/eclipse/paho.mqtt.golang@v1.4.3 · osv@v1

go.sum

GO-2025-4173

github.com/eclipse/paho.mqtt.golang@v1.4.3 · osv@v1

go.sum

GHSA-w67g-5rqw-f597

github.com/gorilla/websocket@v1.5.0 · osv@v1

go.sum

GO-2026-6278

github.com/gorilla/websocket@v1.5.0 · osv@v1

go.sum

GHSA-45gg-vh54-h5m9