Lots of room to improve. Start with a README and CI.
Software Tracking System helps to effectively manage the time and resources of the project as per the requirements of the company. It gives a clear notion of how the employee effort is distributed amongst the ongoing projects. It provides the necessary input for financial and HR accounting and keeps a record of each project’s total effort. The main users of this are: clients to whom the completed project is to be given, project leader who coordinates all the activities of the project and developers who helps to develop the project.
Documentation
0
No README found in the repository.
→ Add a README.md describing what the project does, how to install it, and how to run it.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
Engineering
0
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 dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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.
Project health
23
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Repository has a description.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 0Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files20 root entries
- 1 (1).csv
- 1 (2).csv
- cer.docx
- certificate.docx
- chapters.docx
- feed (1).csv
- feed (2).csv
- feeds (4).csv
- feeds (5).csv
- final project report.pdf
- FINAL REPORT (1).docx
- FRONT PAGES.docx
- front.docx
- lastdoc B.pdf
- major project.pdf
- MCA Major Project 2020 Report Guidelines & Format.pdf
- PPT PRJCT-1.pptx
- project final report.pdf
- reprt.pdf
- SYSTEM STUDY.docx