keymelt/iot_project
Grade a repo

0

/ 100

GradeA

Excellent work. The main thing left to polish is dependency metadata. It just hasn't found an audience yet.

Top 4% of 5,156 graded repos

The Asset Tracker project tracks the location and motion of assets using GPS and accelerometer data. Integrated with the Blynk IoT platform, it provides real-time location updates and accident detection alerts. This project demonstrates the use of sensors for remote monitoring and safety applications.

Documentation98
Engineering100
Health89
C++2MIT1d ago

Outstanding. A score of 97/100 puts this repo in a very small tier of truly well-engineered projects.

Top fixes

Highest-impact changes first, ranked by point weight

6 to address
  1. 1
    Dependency manifest6pt

    Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.

  2. 2
    Dependency manifest6pt

    Add a `keywords` array to help people find your package on npm.

  3. 3
    Dependency manifest6pt

    Add a `homepage` field pointing to your docs or project website.

  4. 4
    Dependency manifest6pt

    Add a `build` script to package.json so the project can be compiled with `npm run build`.

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

98

Contributing guide5pt87

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

100

Tests18pt100

Test files detected (tests).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Reproducibility6pt100

Lockfile present (package-lock.json). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

Dependency manifest found (package.json).

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)
  • 0
    Forks
  • 0
    Releases

Community

  • 100% - Good
    Community health
  • -
    authors own >50% of commits
  • 2
    Watchers

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 6
    Open issues
Repository files21 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 4 ecosystems (github-actions, docker, npm, pip). Dependencies stay current.
    Good: Issue or PR templates present.
  • schematics
  • scripts
  • tests
    Good: Test files detected (tests).
  • TrackerCode
  • .clang-format
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • LICENSE
    Good: Licensed under MIT.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • platformio.ini
  • 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.
  • requirements.lock
  • requirements.txt
  • 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/keymelt/iot_project)](https://www.repo-grade.com/report/keymelt/iot_project)

More graded C++ repos