ton-blockchain/acton
Grade a repo

89

/ 100

GradeB

Well engineered. The main gaps are CI and dependency metadata.

Top 14% of 5,156 graded repos

Toolchain for TON smart contract development and beyond

Documentation95
Engineering85
Health89
Rust427Apache-2.04d ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    CI/CD14pt

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

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

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

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

95

README12pt90

README is present.

Contributing guide5pt93

Contributing guide is detailed and thorough.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

85

CI/CD14pt57

CI is configured (.github/workflows/build-actonscan-backend-docker-image.yml).

Reproducibility6pt80

Lockfile present (Cargo.lock). Installs are reproducible.

Tests18pt100

Test files detected (apps/faucet/tests).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

Dependency manifest found (Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 69
    Forks
  • 39
    Releaseslatest 5mo ago

Community

  • 75% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 427
    Watchers

Responsiveness

  • 58d 23h
    Median issue response
  • <1h
    Median PR merge time
  • 33
    Open issues
Repository files42 root entries
  • .cargo
  • .config
  • .github
    Good: CI is configured (.github/workflows/build-actonscan-backend-docker-image.yml).
    Good: Issue or PR templates present.
  • apps
    Good: Test files detected (apps/faucet/tests).
  • assets
  • crates
    Good: Licensed under Apache-2.0.
  • docs
  • lib
  • packages
  • src
  • tests
  • xtask
  • _typos.toml
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • Acton.toml
  • biome.jsonc
  • build.rs
  • bun.lock
  • bunfig.toml
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • clippy.toml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • dist-workspace.toml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • justfile
  • LICENSE-APACHE
  • LICENSE-MIT
  • netlify.toml
  • osv-scanner.toml
  • package.json
  • 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.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • RELEASING.md
  • rust-toolchain.toml
  • rustfmt.toml
  • SECURITY.md
    Good: Security policy present.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/ton-blockchain/acton)](https://www.repo-grade.com/report/ton-blockchain/acton)

More graded Rust repos