injectivelabs/injective-lists
Grade a repo

0

/ 100

GradeF

Getting some notice. Tests and CI would be the fastest wins.

A place to store JSON lists for different purposes.

Documentation51
Engineering30
Health100
TypeScript15today

Documentation

51

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

Contributing guide5pt64

Contributing guide is detailed and thorough.

README12pt75

README is present.

Engineering

30

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

CI/CD14pt40

CI is configured (.github/workflows/master.yaml).

Reproducibility6pt70

Lockfile present (src/pnpm-lock.yaml). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (src/.prettierrc.js).

Project health

100

Dependency manifest6pt100

Dependency manifest found (src/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)
  • 31
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 15
    Watchers

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 3
    Open issues
Repository files8 root entries
  • .github
    Good: CI is configured (.github/workflows/master.yaml).
  • json
  • src
    Good: Linter or formatter configured (src/.prettierrc.js).
    Good: Lockfile present (src/pnpm-lock.yaml). Installs are reproducible.
    Good: Dependency manifest found (src/package.json).
  • tokens
  • .gitignore
    Good: .gitignore 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.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • NOTICE.md
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
    Good: README documents how to run the project.