RustPython/RustPythonNew scan
90/ 100 · A

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

A Python Interpreter written in Rust

Rust22,115 starsMITupdated 2d ago
DocumentationREADME, setup, examples, license
96
EngineeringTests, CI, linting, lockfiles
91
Project healthDescription, activity, stars, deps
80

What to fix first

The highest-impact improvements for this repo.

  1. 1
    Install and run instructions
    DocumentationInfo

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

  2. 2
    Reproducibility
    EngineeringInfo

    Add `edition = "2021"` to [package] in Cargo.toml for the latest Rust language features.

  3. 3
    Issue and PR templates
    EngineeringInfo

    A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.

Detailed breakdown

Documentation

96
  • README100
    • README is present.
    • README is well structured with multiple sections.
    • README includes screenshots or visuals. Great for first impressions.
    • README has code examples.
    • README links to a live demo or deployed app.
    • README includes status badges.
  • Install and run instructions90
    • README documents how to install the project.
    • README documents how to run the project.
    • If your project uses environment variables, add a .env.example listing them (+10 pts).Add a .env.example listing all required environment variables so contributors know what to set up.
  • License100
    • Licensed under MIT.
  • Contributing guide90
    • Contributing guide is detailed and thorough.
    • Contributing guide includes setup/install instructions.
    • Contributing guide describes code style expectations.
    • Contributing guide explains how to run tests.
    • Contributing guide lacks a PR workflow section (−8 pts).Explain how to fork, branch, and open a pull request so contributors know what to expect.
    • Contributing guide includes code examples.
    • Optional: add a Code of Conduct (+5 pts).A CODE_OF_CONDUCT.md signals that your project is welcoming. GitHub has a template you can add in one click.

Engineering

91
  • Tests90
    • Test files detected (Lib/test).
    • Cargo.toml has dev-dependencies and test files are present.
  • CI/CD100

    Not applicable?

    • CI is configured (.github/workflows/ci.yaml).
    • CI workflow runs tests.
    • CI runs on pull requests, not just on pushes to main.
    • CI workflow runs a lint or format check.
    • CI runs type checking (tsc, mypy, cargo check, etc.).
    • CI reports or uploads test coverage.
    • CI caches dependencies for faster runs.
    • CI tests across multiple environments or versions.
    • CI includes a build step.
  • Linting and formatting60
    • Linter or formatter configured (.flake8).
  • Reproducibility100
    • Lockfile present (Cargo.lock). Installs are reproducible.
    • Environment pinned via .devcontainer/Dockerfile.
    • Dependabot covers 4 ecosystems (cargo, github-actions, npm, pre-commit). Dependencies stay current.
    • Cargo.toml does not specify edition 2021.Add `edition = "2021"` to [package] in Cargo.toml for the latest Rust language features.
  • Issue and PR templates90
    • Issue or PR templates present.
    • Optional: add a SECURITY.md.A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.

Project health

80
  • Dependency manifest70
    • Dependency manifest found (Cargo.toml).
    • Cargo.toml includes a description for crates.io.
    • Cargo.toml is missing a license field (−10 pts).Add `license = "MIT"` (or your preferred SPDX identifier) to [package].
    • Cargo.toml is missing a repository field (−10 pts).Add `repository = "https://github.com/owner/repo"` to [package].
  • Repository metadata85
    • Repository has a description.
    • Primary language detected: Rust.
  • Activity100
    • Actively maintained (pushed within the last month).
    • 22,115 stars.
  • Housekeeping60
    • .gitignore present.
    • Build artifacts or local files may be committed (Lib/venv/__init__.py) (−40 pts).Remove them and add to .gitignore.
Repository files52 root entries
  • .agents
  • .cargo
  • .claude
  • .cspell.dict
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .gemini
  • .github
    Good: CI is configured (.github/workflows/ci.yaml).
    Good: Dependabot covers 4 ecosystems (cargo, github-actions, npm, pre-commit). Dependencies stay current.
    Good: Issue or PR templates present.
  • .theia
  • .vscode
  • architecture
  • benches
  • crates
  • example_projects
  • examples
  • extra_tests
  • installer-config
  • Lib
    Good: Test files detected (Lib/test).
    Warning: Build artifacts or local files may be committed (Lib/venv/__init__.py) (−40 pts).Fix: Remove them and add to .gitignore.
  • scripts
  • src
  • tools
  • wasm
  • .coderabbit.yml
  • .cspell.json
  • .dockerignore
  • .flake8
    Good: Linter or formatter configured (.flake8).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitpod.Dockerfile
  • .gitpod.yml
  • .mailmap
  • .pre-commit-config.yaml
  • .python-version
  • AGENTS.md
  • build.rs
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • code-of-conduct.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Info: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • deny.toml
  • Dockerfile.bin
  • Dockerfile.wasm
  • host_env_proposal.md
  • LICENSE
    Good: Licensed under MIT.
  • LICENSE-logo
  • logo.ico
  • logo.png
  • pdc.sh
  • 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.
  • ruff.toml
  • rust-toolchain.toml
  • rustfmt.toml
  • wapm.toml