Safety rating · all ratings

N1nEmAn/sapper-v2

Score 46/100 — Limited 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 46/100 — Limited public signals. As of 2026-11-06T15:28:07.678Z (check version rs-safety-checks-1.0). Repository: https://github.com/N1nEmAn/sapper-v2

Checks

• License present (OSI-approved) — Found (10/10): GitHub detects license MIT (OSI-approved). Source: https://api.github.com/repos/N1nEmAn/sapper-v2
• Security policy (SECURITY.md) — Not found (0/8): No SECURITY.md found in the repository root, the .github folder or the docs folder. Source: https://api.github.com/repos/N1nEmAn/sapper-v2/git/trees/master?recursive=1
• Known advisories in pinned dependencies (OSV) — Not applicable: No supported lockfile with pinned versions was found, so no packages were checked against OSV.
• OpenSSF Scorecard — Not applicable: No published OpenSSF Scorecard result for this repository. Source: https://api.securityscorecards.dev/projects/github.com/N1nEmAn/sapper-v2
• Signed releases or build provenance — Not found (0/8): No signature, attestation or provenance signals in workflows or in the last 1 releases. Source: https://api.github.com/repos/N1nEmAn/sapper-v2/releases
• Continuous integration present — Not found (0/8): No CI configuration found. Source: https://api.github.com/repos/N1nEmAn/sapper-v2/git/trees/master?recursive=1
• Credential-pattern scan — Found (12/12): No credential patterns matched in 27 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/N1nEmAn/sapper-v2/git/trees/master?recursive=1
• Pinned dependencies — Not found (0/9): Lockfiles: none found. GitHub Actions pinned to a commit SHA: no third-party actions. Automated update config: none found. Source: https://api.github.com/repos/N1nEmAn/sapper-v2/git/trees/master?recursive=1
• Maintainer activity — Partly found (8/10): Last commit 3 day(s) before the check; 13 commits by 2 distinct author(s) in the prior 90 days. Source: https://api.github.com/repos/N1nEmAn/sapper-v2/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 #16735 at 2026-11-06T15:41:25.255Z: score 46, rs-safety-checks-1.0, rating 182f65a791ae5672…

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/N1nEmAn/sapper-v2/recheck. Badge: https://www.rightshold.com/v1/safety-ratings/N1nEmAn/sapper-v2/badge.svg