tauri-apps/tauriNew scan
88/ 100 · B

A landmark open source project with strong engineering quality.

Build smaller, faster, and more secure desktop and mobile applications with a web frontend.

Rust107,877 starsApache-2.0updated 2d ago
DocumentationREADME, setup, examples, license
93
EngineeringTests, CI, linting, lockfiles
87
Project healthDescription, activity, stars, deps
84

What to fix first

The highest-impact improvements for this repo.

  1. 1
    CI/CD
    EngineeringWarning

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

  2. 2
    CI/CD
    EngineeringInfo

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

  3. 3
    Install and run instructions
    DocumentationInfo

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

Detailed breakdown

Documentation

93
  • 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 Apache-2.0.
  • Contributing guide75
    • CONTRIBUTING guide or docs directory present.
    • Code of conduct present.

Engineering

87
  • Tests100
    • Test files detected (bench/tests).
  • CI/CD72

    Not applicable?

    • CI is configured (.github/workflows/check-change-tags.yml).
    • The CI workflow does not appear to run any tests (−28 pts).Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
    • 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.).
    • Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
    • CI includes a build step.
  • Linting and formatting75
    • Linter or formatter configured (.editorconfig).
    • Lint script wired into package.json.
  • Reproducibility80
    • Lockfile present (Cargo.lock). Installs are reproducible.
    • Environment pinned via .devcontainer/Dockerfile.
    • No Dependabot config (adding it earns up to +20 pts).Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
  • Issue and PR templates100
    • Issue or PR templates present.
    • Security policy present.

Project health

84
  • Dependency manifest75
    • Dependency manifest found (Cargo.toml).
    • package.json is missing a description (−10 pts).Add a one-line description to package.json. It appears in npm search and on GitHub.
    • package.json links back to the repository.
    • package.json has no keywords (−8 pts).Add a `keywords` array to help people find your package on npm.
    • package.json has no homepage field (−7 pts).Add a `homepage` field pointing to your docs or project website.
  • Repository metadata70
    • Repository has a description.
    • Primary language detected: Rust.
  • Activity100
    • Actively maintained (pushed within the last month).
    • 107,877 stars.
  • Housekeeping100
    • .gitignore present.
Repository files31 root entries
  • .cargo
  • .changes
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .docker
  • .github
    Good: CONTRIBUTING guide or docs directory present.
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/check-change-tags.yml).
    Good: Issue or PR templates present.
  • .scripts
  • .vscode
  • audits
  • bench
    Good: Test files detected (bench/tests).
  • crates
  • examples
  • packages
  • supply-chain
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .prettierignore
  • .prettierrc
  • ARCHITECTURE.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • dependabot.yml
  • LICENSE_APACHE-2.0
  • LICENSE_MIT
  • LICENSE.spdx
    Good: Licensed under Apache-2.0.
  • package.json
  • pnpm-lock.yaml
  • pnpm-workspace.yaml
  • 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.
  • renovate.json
  • rustfmt.toml
  • SECURITY.md
    Good: Security policy present.