0
/ 100
Getting noticed, but rough fundamentals could turn visitors away.
High performance data processing employs high performance computing (HPC) to process data, which is then translated into information and knowledge. The advent of high-performance computing and data analytics enabled real-time interrogation of extremely large data sets.
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (72).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
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.
- 3README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 4Install and run instructions9pt
Add a section showing how to install dependencies.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
48
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Engineering
10
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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 (2425/project/p2/CrawlOps/dashboard/package-lock.json). Installs are reproducible.
Project health
94
.gitignore present.
Dependency manifest found (2425/project/p2/CrawlOps/dashboard/package.json).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 138Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 153Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 11Open issues
Repository files13 root entries
- 2425Good: Lockfile present (2425/project/p2/CrawlOps/dashboard/package-lock.json). Installs are reproducible.Good: Environment pinned via 2425/project/p2/GroupA/kafka_spark_pipeline/docker-compose.yml.Good: Dependency manifest found (2425/project/p2/CrawlOps/dashboard/package.json).Good: .gitignore present.
- 2526
- assignment
- exercise
- images
- lab
- materials
- portfolio
- .DS_StoreIssue: Build artifacts or local files may be committed (.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
- grab_reviews_raw.csv
- README.mdGood: 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.Good: README includes status badges.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.
- sem2223.md
- student.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/drshahizan/hpdp)