Code health of parse-community/parse-server
Repowise scores parse-community/parse-server at 6.5 out of 10 for code health, which reads as fair, alongside maintainability 7.2 and static performance 9.9 on the same scale. There are 1,044 open findings across the three pillars, and the lowest-scoring file is UsersRouter.js at 1.6. Scores are computed from complexity, duplication, churn and git fix history, not from a linter.
Findings by severity
105 critical, 220 high, 299 medium, 309 low.
Hotspots
4 files are flagged as hotspots. The top 4:
- src/Options/Definitions.js: 4 commits in the last 90 days from 21 contributors with 2 recent bug fixes
- src/GraphQL/ParseGraphQLServer.js: 5 commits in the last 90 days from 6 contributors with 6 recent bug fixes
- src/Options/index.js: 3 commits in the last 90 days from 21 contributors with 1 recent bug fix
- src/Options/docs.js: 3 commits in the last 90 days from 20 contributors with 1 recent bug fix
Lowest-scoring files
- src/Routers/UsersRouter.js: 1.6 out of 10 with 7 bug fixes in the last 180 days
- src/RestQuery.js: 1.9 out of 10 with 5 bug fixes in the last 180 days
- src/Adapters/Storage/Mongo/MongoTransform.js: 1.9 out of 10
- src/middlewares.js: 2.1 out of 10 with 6 bug fixes in the last 180 days
- src/Controllers/SchemaController.js: 2.1 out of 10
Checked against bug fixes
Of the 20 files Repowise scores lowest, 13 had a bug fix in the last 180 days. Across all 389 scored files, 18.0% had a bug fix in that window.
Dead code and refactoring
Repowise found 15 unused exports. 57 refactoring targets across 57 files would raise the score.
More on parse-server: summary and FAQ, codebase overview, architecture.
Related guide: Best dead code detection tools by language