parse-community / parse-server
Parse Server for Node.js / Express
github.com/parse-community/parse-serverIndexed at 278f33aUp to date with upstream
About this codebase
Parse Server is a backend engine that consumes incoming HTTP requests (REST/SDK calls and GraphQL queries) and produces Parse-compatible responses by routing requests, validating permissions/security, persisting or fetching objects, and handling cross-cutting services like pushes, file uploads, and authentication via configurable adapters. End-to-end, `parse-server` accepts configuration (options object or a JSON configuration file), performs asynchronous initialization to avoid mounting before readiness, then continuously serves request handlers mounted in Express/Fastify-style runtimes; the primary artifacts are a running Parse API surface (including `/parse/health`) plus the internal services/controllers that power core operations (auth, queries, permissions, page/template localization, and security checks).
Written by gpt-5.4-nano from the index
454 files and 1,770 symbols in 9 modules, led by JavaScript (364 files) and TypeScript (12).
Code health
This codebase scores 6.5 out of 10 for code health, which we rate fair. It also scores maintainability 7.2 and static performance 9.9 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 6 of 454 files are git hotspots, and they average 3.6 — which is where the fixes pay off most.
On the leaderboards:#7 of 12 JavaScript repos
Do next
1 thing worth doing in the week to Sep 23, the last indexed commit, 1 of them now.
Now
- High
Simplify
stripSchemaTypeIdentifiersinsrc/GraphQL/ParseGraphQLServer.jswhile the change is fresh1 commit in the last 7 days added or worsened 1 critical or high finding here, still open. Fixing now costs less than after the next change.
- serious findings
- 1
- critical
- 0
- latest commit
- fix: GraphQL argument and enum validation errors disclose target class n
Small effort
Improve what Repowise can see
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
- line coverage
- Unknown, no report
Small effort
Use parse-community/parse-server in your agent
Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.
https://api.repowise.dev/mcp/parse-community/parse-serverOne command, run anywhere. Adds the server to your local Claude Code config.
Docsclaude mcp add --transport http repowise https://api.repowise.dev/mcp/parse-community/parse-server \ --header "Authorization: Bearer rw_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
This repo is public, so anyone with a Repowise account and an API key can connect.
Try asking
- get_overview()
- get_answer("how is parse-server put together?")
- get_why("why is parse-server structured this way?")
Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.
Go deeper
- OverviewEverything the index found, what changed this week, commits and decisions.
- DocumentationModule-by-module documentation, 417 pages, 25 written by a model.
- ArchitectureDependency graph, layers and third-party dependencies.
- Code healthEvery file's score, the findings behind it, tests and refactoring plans.
- CommitsEach commit's effect on code health, with agent provenance.
- ContributorsWho owns what, and where one person holds most of the knowledge.
- DecisionsArchitectural decisions mined from commits and pull requests.
- Ask this codebaseSign inGrounded answers over the indexed code.
Maintain this repo? Claim the page
Sign in with GitHub and we check that you are an admin or maintainer of parse-community/parse-server. Then add a badge to the README that links readers here.
Use this repo from Claude or ChatGPT
Add this URL as a custom connector and sign in with repowise when asked. No API key to copy.
https://api.repowise.dev/mcp/parse-community/parse-serverFor maintainers
Add a badge to your README
Every badge is public, cached, and updates on its own after every index. Nothing to install.
Repowise badge
Links to this page, with no score on it. Adding it also re-indexes the repo every week.
[](https://repowise.dev/repo/parse-community/parse-server?src=badge_wiki)Code health badge
The repo's health score out of 10, from the latest index.
[](https://repowise.dev/repo/parse-community/parse-server?src=badge_health)Code health card
A larger card with the score, its change since the last index, and when it was measured. The HTML version follows the reader's light or dark theme.
[](https://repowise.dev/repo/parse-community/parse-server?src=badge_card)How parse-community/parse-server works
Parse Server for Node.js / Express This page is a map of the parse-community/parse-server repository, written primarily in JavaScript, rebuilt from the source each time it is indexed. Repowise parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the architectural decisions into documentation you can read here or query through MCP.
The codebase has 454 files and 1,770 symbols in 9 modules, led by JavaScript, TypeScript and Shell. Code health is 6.5 out of 10, rated fair.
Use the links above to open each view, or connect this repository to your agent for grounded answers inside Claude, Cursor, Codex or VS Code.