sakha1370/openray

0

/ 100

Documentation38
Engineering11
Health62
Python2181d ago
Grade a repo

Getting noticed, but rough fundamentals could turn visitors away.

OpenRay is one of the largest open-source collections of free proxy servers, running hourly pipelines to ensure high-quality lists by protocol and country, promoting open and unrestricted internet access for everyone worldwide.

Documentation

38

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt100

README is present.

Engineering

11

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

CI/CD14pt40

CI is configured (.github/workflows/check-new-proxies.yml).

Project health

62

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

Housekeeping3pt60

.gitignore present.

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)
  • 19
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 218
    Watchers

Responsiveness

  • 22d 13h
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files31 root entries
  • .github
    Good: CI is configured (.github/workflows/check-new-proxies.yml).
  • .idea
    Issue: Build artifacts or local files may be committed (.idea/.gitignore) (−40 pts).Fix: Remove them and add to .gitignore.
  • .state
  • docs
  • output
  • output_iran
  • scripts
  • src
  • .gitignore
    Good: .gitignore present.
  • auto_update.sh
  • BrokenSource.txt
  • change_iran.py
  • change.py
  • check_dedup_file.py
  • check_duplicates_proper.py
  • check_duplicates.py
  • check_parameters.py
  • clean_data.py
  • clean_history.py
  • clean_proxy_files.py
  • generate_operator_rankings.py
  • manage_tested_files.py
  • migrate_check_counts.py
  • optimize_storage.py
  • 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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • repro_concurrency.py
  • requirment.txt
  • small.txt
  • sources_iran.txt
  • sources.txt
  • xray-install.sh