slint-ui/slintNew scan
77/ 100 · C

Popular and well-maintained. A little polish away from elite status.

Slint is an open-source declarative GUI toolkit to build native user interfaces for Rust, C++, JavaScript, or Python apps.

Rust22,893 starsOtherupdated 2d ago
DocumentationREADME, setup, examples, license
92
EngineeringTests, CI, linting, lockfiles
67
Project healthDescription, activity, stars, deps
78

What to fix first

The highest-impact improvements for this repo.

  1. 1
    Tests
    EngineeringWarning

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD
    EngineeringInfo

    Add `pull_request:` to the workflow `on:` triggers.

  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

92
  • 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 Other.
  • Contributing guide67
    • Contributing guide is present (+6 pts for length); 400+ words earns the full +12 pts.
    • Contributing guide lacks a setup section (−12 pts).Show new contributors how to get a local dev environment running.
    • Contributing guide describes code style expectations.
    • Contributing guide lacks a testing section (−8 pts).Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    • Contributing guide describes the PR/review workflow.
    • Contributing guide has no code examples (−5 pts).Add code blocks showing example commands for setup, running tests, and submitting a PR.
    • 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

67
  • Tests35
    • Test files detected (api/cpp/tests).
    • The npm test script is the default placeholder. Running `npm test` will fail.Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".
  • CI/CD83

    Not applicable?

    • CI is configured (.github/workflows/build_and_test_reusable.yaml).
    • CI workflow runs tests.
    • CI does not appear to trigger on pull requests (−17 pts).Add `pull_request:` to the workflow `on:` triggers.
    • 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 formatting75
    • Linter or formatter configured (api/node/biome.json).
    • Lint script wired into package.json.
  • Reproducibility90
    • Lockfile present (Cargo.lock). Installs are reproducible.
    • No Dockerfile or runtime version pin found. Adding one earns +10 pts.Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
    • Dependabot covers 2 ecosystems (github-actions, npm). Dependencies stay current.
  • Issue and PR templates100
    • Issue or PR templates present.
    • Security policy present.

Project health

78
  • Dependency manifest55
    • 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 has no repository field (−10 pts).Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.
    • 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.
    • package.json has no build script (−10 pts).Add a `build` script to package.json so the project can be compiled with `npm run build`.
  • Repository metadata70
    • Repository has a description.
    • Primary language detected: Rust.
  • Activity100
    • Actively maintained (pushed within the last month).
    • 22,893 stars.
  • Housekeeping100
    • .gitignore present.
Repository files54 root entries
  • .cargo
  • .claude-plugin
  • .cspell
  • .cursor-plugin
  • .github
    Good: CI is configured (.github/workflows/build_and_test_reusable.yaml).
    Good: Dependabot covers 2 ecosystems (github-actions, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • .mise
  • .vscode
  • api
    Good: Test files detected (api/cpp/tests).
    Good: Linter or formatter configured (api/node/biome.json).
  • cmake
  • demos
  • docker
  • docs
  • editors
  • examples
  • helper_crates
  • internal
  • LICENSES
  • logo
  • scripts
  • skills
  • tests
  • tools
  • ui-libraries
  • xtask
  • .clang-format
  • .clippy.toml
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • .npmrc
  • .taplo.toml
  • AGENTS.md
  • biome.json
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
    Good: Contributing guide is present (+6 pts for length); 400+ words earns the full +12 pts.
    Info: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    Info: 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.
    Info: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • CMakeLists.txt
  • CMakePresets.json
  • CONTRIBUTING.md
  • Cross.toml
  • cspell.json
  • FAQ.md
  • flake.lock
  • flake.nix
  • knip.json
  • LICENSE.md
    Good: Licensed under Other.
  • 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.
  • REUSE.toml
  • rustfmt.toml
  • SECURITY.md
    Good: Security policy present.