openai/snap-o
Grade a repo

78

/ 100

GradeC

Solid foundation. Invest in docs and CI to grow from here.

Top 35% of 5,156 graded repos

Lightweight Android capture developer tools for macOS

Documentation95
Engineering61
Health94
Swift84Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

7 to address
  1. 1
    Tests18pt

    Add automated tests. They prove the code works and give contributors confidence to make changes.

  2. 2
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  3. 3
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

  4. 4
    Contributing guide5pt

    Add setup instructions, code style notes, and how to run tests.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

95

Contributing guide5pt83

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

61

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Reproducibility6pt80

Lockfile present (snapo-network-inspector-web/package-lock.json). Installs are reproducible.

CI/CD14pt100

CI is configured (.github/workflows/android-link.yml).

Linting and formatting5pt100

Linter or formatter configured (snapo-app-mac/.swiftlint.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (snapo-link-android/build-logic/build.gradle.kts).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 38 / 50
    Commits (30d / 90d)
  • 15
    Forks
  • 25
    Releaseslatest 9mo ago

Community

  • 75% - Good
    Community health
  • -
    authors own >50% of commits
  • 84
    Watchers

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files14 root entries
  • .codex
  • .github
    Good: CI is configured (.github/workflows/android-link.yml).
    Good: Issue or PR templates present.
  • design-audits
  • skills
  • snapo-app-mac
    Good: Linter or formatter configured (snapo-app-mac/.swiftlint.yml).
    Good: Environment pinned via snapo-app-mac/mise.toml.
  • snapo-link-android
    Good: Dependency manifest found (snapo-link-android/build-logic/build.gradle.kts).
    Issue: Build artifacts or local files may be committed (snapo-link-android/.idea/.gitignore) (−40 pts).Fix: Remove them and add to .gitignore.
  • snapo-network-inspector-web
    Good: Lockfile present (snapo-network-inspector-web/package-lock.json). Installs are reproducible.
  • .gitignore
    Good: .gitignore present.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • jitpack.yml
  • LICENSE
    Good: Licensed under Apache-2.0.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • VERSION
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/openai/snap-o)](https://www.repo-grade.com/report/openai/snap-o)

More graded Swift repos