ljcoder2015/obsidian-sheet-plus

0

/ 100

Documentation47
Engineering22
Health95
TypeScript415Apache-2.01d ago
Grade a repo

Getting noticed, but rough fundamentals could turn visitors away.

obsidian spreadsheets solutions

Documentation

47

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt75

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

22

Tests18pt0

No tests detected anywhere in the repository.

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

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.

Linting and formatting5pt100

Linter or formatter configured (eslint.config.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

95

Dependency manifest6pt83

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)
  • 28
    Forks
  • 124
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 7d 3h
    Median issue response
  • <1h
    Median PR merge time
  • 35
    Open issues
Repository files15 root entries
  • .github
    Good: Issue or PR templates present.
  • images
  • patches
  • scripts
  • src
  • .gitignore
    Good: .gitignore present.
  • .release-it.json
  • CHANGELOG.md
  • eslint.config.js
    Good: Linter or formatter configured (eslint.config.js).
  • LICENSE
    Good: Licensed under Apache-2.0.
  • manifest.json
  • package.json
    Good: Dependency manifest found (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.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • tsconfig.json
  • vite.config.ts