parse-community / parse-community/parse-server
3rd party module disclaimer
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
The docs list email adapters for Parse Server maintained by 3rd parties. The Parse Platform has no control over their security and fitness for use. For example, for parse-server-mailgun has last been published 2 years ago and has several unmaintained dependencies.
Especially for new developers who just add the dependency to Parse Server, this may not be an obvious issue. They may not even be aware that these modules are not provided by and scrutinized as part of the Parse Platform product suite.
Suggestion
Clearly mark references to 3rd party repos and add a disclaimer.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Parse Server documentation at the Email Verification and Password Reset section linked in the issue, and review how the parse-server-mailgun and other third-party adapters are referenced. Mark third-party repositories clearly and add a disclaimer explaining that Parse Platform does not control their security or maintenance; the documentation should make this distinction obvious to new developers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100