asevans48/tokio

0

/ 100

Documentation58
Engineering94
Health64
0MIT6y ago
Grade a repo

Solid engineering. The main gap is visibility.

A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...

Documentation

58

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

README12pt70

README is present.

Contributing guide5pt80

Contributing guide is detailed and thorough.

License6pt100

Licensed under MIT.

Engineering

94

Reproducibility6pt50

No Cargo.lock committed (correct for Rust library crates; the ecosystem convention is to omit it for libraries).

Tests18pt100

Test files detected (tests-build/tests).

CI/CD14pt100

CI is configured (azure-pipelines.yml).

Linting and formatting5pt100

Rust linting configured (rustfmt.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

64

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Repository metadata5pt60

Repository has a description.

Dependency manifest6pt100

Dependency manifest found (Cargo.toml).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files20 root entries
  • .github
    Good: Issue or PR templates present.
  • bin
  • ci
  • examples
  • tests-build
    Good: Test files detected (tests-build/tests).
  • tests-integration
  • tokio
  • tokio-macros
  • tokio-test
  • tokio-tls
  • tokio-util
  • .cirrus.yml
  • .gitignore
    Good: .gitignore present.
  • azure-pipelines.yml
    Good: CI is configured (azure-pipelines.yml).
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide explains how to run tests.
    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.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    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.
  • ROADMAP.md
  • rustfmt.toml
    Good: Rust linting configured (rustfmt.toml).