adminlove520/ai-account-toolkit
Grade a repo

69

/ 100

GradeD

Strong community interest, but tests, CI, or docs need work.

Top 47% of 5,156 graded repos

AI 账号注册与管理一站式工具集 | ChatGPT, Claude, Gemini, Codex, Cursor, Grok 批量注册、Token 管理、临时邮箱服务

Documentation95
Engineering43
Health94
Python1,020MIT1mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to A (92).

See your top fixes
Now
D
69
Potential
A
92

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    Tests18pt

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

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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 guide5pt66

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.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

43

Tests18pt0

No tests detected anywhere in the repository.

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

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

CI/CD14pt72

CI is configured (.github/workflows/submodule-health-check.yml).

Reproducibility6pt80

Lockfile present (CPAtools/requirements.txt). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (CPAtools/requirements.txt).

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

  • -
    Commits (30d / 90d)
  • 312
    Forks
  • 11
    Releaseslatest 1mo ago

Community

  • 71% - Fair
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 1,020
    Watchers

Responsiveness

  • 18h
    Median issue response
  • -
    Median PR merge time
  • 5
    Open issues
Repository files32 root entries
  • .github
    Good: CI is configured (.github/workflows/submodule-health-check.yml).
    Good: Issue or PR templates present.
  • chatgpt_register_duckmail
  • ClashVerge_
  • Code-Patch
  • codex
    Issue: Build artifacts or local files may be committed (codex/codex-register-cpa/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • codex-oauth-automation-extension
  • codex-register-V2
  • CPAtools
    Good: Lockfile present (CPAtools/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (CPAtools/requirements.txt).
  • Extensions
  • freemail
  • FreeSMS
  • GPT_register+duckmail+CPA+autouploadsub2api
  • GPT-team
  • grok
  • mailhub
  • merge-mailtm-share
  • ob12api
  • openai_pool_orchestrator_v5
  • openai_pool_orchestrator-V6
  • openai_register
  • packages
  • Register_GPT_v0
    Good: Environment pinned via Register_GPT_v0/web/Dockerfile.
  • team
  • team_all-in-one
  • TrezaReg
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • CHANGELOG.md
  • 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.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    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.
  • LICENSE
    Good: Licensed under MIT.
  • 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.
  • update_summary.md
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/adminlove520/ai-account-toolkit)](https://www.repo-grade.com/report/adminlove520/ai-account-toolkit)

More graded Python repos