Rough and inactive. Tests, CI, and a fuller README would revive it.
Documentation
49
README is present.
README documents how to install the project.
CONTRIBUTING guide found.
A license file is present.
Engineering
77
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.
Lockfile present (mynode/node_modules/array-back/yarn.lock). Installs are reproducible.
Test files detected (mynode/node_modules/append-field/test).
CI is configured (mynode/node_modules/ansi-escape-sequences/.travis.yml).
Linter or formatter configured (mynode/node_modules/@xmldom/xmldom/lib/.eslintrc.yml).
Project health
53
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
.gitignore present.
Dependency manifest found (android/app/build.gradle).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 1Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files20 root entries
- .vscode
- androidGood: Dependency manifest found (android/app/build.gradle).
- Assets
- images
- ios
- lib
- mynodeGood: A license file is present.Good: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Test files detected (mynode/node_modules/append-field/test).Good: CI is configured (mynode/node_modules/ansi-escape-sequences/.travis.yml).Good: Linter or formatter configured (mynode/node_modules/@xmldom/xmldom/lib/.eslintrc.yml).Good: Lockfile present (mynode/node_modules/array-back/yarn.lock). Installs are reproducible.Good: Security policy present.Issue: Build artifacts or local files may be committed (mynode/node_modules/.bin) (−40 pts).Fix: Remove them and add to .gitignore.
- test
- uploads
- web
- windows
- .gitattributes
- .gitignoreGood: .gitignore present.
- .metadata
- analysis_options.yaml
- mynode.zip
- newComplaint.dart
- pubspec.lock
- pubspec.yaml
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.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.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.