Safety rating · all ratings

elie222/rakazo

Score 85/100 — Strong public signals

Automated checks of public signals as of the date shown. Not a security audit, certification or endorsement, and not a statement about the people who maintain the project. Signals can be incomplete or out of date; each check shows its evidence and source so anyone can verify it.

Score 85/100 — Strong public signals. As of 2026-11-14T14:54:29.262Z (check version rs-safety-checks-1.0). Repository: https://github.com/elie222/rakazo

Checks

• License present (OSI-approved) — Found (10/10): GitHub detects license Apache-2.0 (OSI-approved). Source: https://api.github.com/repos/elie222/rakazo
• Security policy (SECURITY.md) — Found (8/8): Security policy at SECURITY.md. Source: https://github.com/elie222/rakazo/blob/main/SECURITY.md
• Known advisories in pinned dependencies (OSV) — Partly found (5/15): 1500 pinned packages checked against OSV; 4 have at least one matching advisory (ajv@8.11.0: GHSA-2g4f-4pwh-qvx6; brace-expansion@1.1.18: GHSA-6j4f-fj2g-mc7p, GHSA-q2hr-2g5m-vwhr; deepmerge@4.3.1: GHSA-gcqx-w48m-w2h4; diff@7.0.0: GHSA-73rr-hh4g-fpgx). An advisory match does not mean the project is exploitable. Source: https://osv.dev
• OpenSSF Scorecard — Not applicable: No published OpenSSF Scorecard result for this repository. Source: https://api.securityscorecards.dev/projects/github.com/elie222/rakazo
• Signed releases or build provenance — Found (8/8): Signals: Rakazo-0.11.0.AppImage.sig, Rakazo-0.10.0.AppImage.sig, Rakazo-0.9.0.AppImage.sig. Source: https://api.github.com/repos/elie222/rakazo/releases
• Continuous integration present — Found (8/8): 22 CI configuration file(s), e.g. .github/workflows/ci.yml, .github/workflows/computer-replay.yml, .github/workflows/desktop-macos-screenshot.yml. Source: https://github.com/elie222/rakazo/blob/main/.github/workflows/ci.yml
• Credential-pattern scan — Found (12/12): No credential patterns matched in 75 scanned files (root-level and one-deep text files (≤60, <200KB each) plus up to 15 workflow files at the default branch head); no credential-like file names. Source: https://api.github.com/repos/elie222/rakazo/git/trees/main?recursive=1
• Pinned dependencies — Partly found (7/9): Lockfiles: pnpm-lock.yaml. GitHub Actions pinned to a commit SHA: 99/99. Automated update config: none found. Source: https://api.github.com/repos/elie222/rakazo/git/trees/main?recursive=1
• Maintainer activity — Found (10/10): Last commit 0 day(s) before the check; 100+ commits by 12 distinct author(s) in the prior 90 days. Source: https://api.github.com/repos/elie222/rakazo/commits
• MCP: tool permissions, access scope and injection notes — Not applicable: Not identified as an MCP server, so MCP-specific checks do not apply.

Ledger

• Entry #45017 at 2026-11-14T15:05:18.187Z: score 85, rs-safety-checks-1.0, rating a465466787bbb916…

Full record — seals, timeline and claim state: https://www.rightshold.com/ratings/browse/github/elie222/rakazo

Witness reciprocity

Your records finalize when the network witnesses; witness the head and yours finalize too. A record on this ledger is final only when its block is confirmed in Bitcoin and cosigned by the current quorum of confirmed-unaffiliated witnesses (2 of 0 confirmed today). Every rated page — including this one — climbs the same ladder, so a maintainer who witnesses the head is doing the exact work that finalizes their own record. Witnessing is free, needs a domain you control and an Ed25519 key, and the kit verifies the whole chain itself before it signs anything. Witness kit: https://www.rightshold.com/cli/witness-in-a-box.mjs (SHA-256: e673093913785d32b472fa45cb60d924fc60047a3b1618c371704038fc83754b). Witness health: https://www.rightshold.com/v1/witnesses/health. Witnessing, claiming a page, or partnering never changes a rating, a record, a ranking or visibility — for partners and strangers alike. A witness cosigns block headers it has checked; it does not speak for any rated project, and no rating reads witness state.

Maintainers

Are you a maintainer? Request a free re-check after changes, or send a response: POST https://www.rightshold.com/v1/safety-ratings/elie222/rakazo/recheck. Badge: https://www.rightshold.com/v1/safety-ratings/elie222/rakazo/badge.svg